Storage Queues are cheaper and more performant than azure service bus if guaranteed first-in-first-out, etc is not required.

They do offer 'At-Least-Once' guaranteed delivery, where Redis is 'fire and forget'.

Combining this with full featured CosmoDb caching instead of Redis would make a compelling low-cost option.

I think that ServiceStack TypeScript client does not work in NativeScript + Angular2 applications, as I am getting a bunch of weird errors when trying that (in Fetch module).

I installed the module as this:
npm install --save @servicestack/client

Is there support for the TypeScript client in NativeScript applications? If not, Id like there to be =)

The Redis client supports distributed locks, which is a really useful feature, the same is possible using DynamoDB.

Reference Implementation:
https://github.com/awslabs/dynamodb-lock-client

While some methods of SqlExpression<T> supports up to 15 generic parameters (Where, And, Or) others like Select, SelectDistinct and GroupBy only supports a couple. When building complex queries, it's easy to select data from more than 7 tables, or group by fields from more than 4 tables.

Could you implement more Select, SelectDistinct and GroupBy overloads like you did for Where, And and Or?

There is no specific number of parameters needed, but I think that the default 15 is a good start.

Right now, bools are serialized uppercase since that's the default ToString behavior of .NET.

Consider changing this behavior by checking for bool when serializing and using .ToString().ToLower(), or introduce a setting to control this. It's web standard to use lowercase bools in query strings.

More info/discussion:
https://github.com/ServiceStack/Issues/issues/586

Support Condition Expressions for PutItem, UpdateItem and DeleteItem operations.

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ConditionExpressions.html

Add SAML 2.0 as built in auth provider. Really useful for Azure AD SSO.

Microservice is the modern and hot trending architectural design pattern now, ServiceStack should has builtin feature to support building microservice. In Java world they have Spring Boot / Spring Cloud to wire together other open source technologies such as Nextflix Ribbon, Eureka, Kafka etc. to build microservice.

Basically, ServiceStack should be identified itself to be not only a framework of choice to build not only RESTful webservice but also a full-fledged platform such as the Java's Spring framework

Currently when a field is marked as IsRequired=true via the OpenAPI attribute it has no relevance to validation. However, it seems very reasonable that when someone marks a field as required, they would want validation that said field was indeed supplied in the DTO. Enabling validation on metadata attributes natively would provide developers this funcitonality without requiring they write a seperate validation method which also lists the required fields.

It would be a good idea for users when using Service Stack Authentication to have functionality like Asp.net Identity to Verify their account, reset their password.

In order to improve security it would be beneficial to change cookie names from const to a configurable option. It would help mask the presence of service stack and improve security in accordance with OWASP recommendations - https://www.owasp.org/index.php/Session_Management_Cheat_Sheet#Session_ID_Name_Fingerprinting

Please implement Brotli compression support for request and response payloads. (-:

There exists a few C# libraries, like this one: https://github.com/XieJJ99/brotli.net

Add a MQ Server for MSMQ that implements ServiceStack's Messaging API: http://docs.servicestack.net/messaging

Hi

In my application user can define multiple filters for specific type. I would like to somehow combine these queries in single one.

SqlExpression<Notice> query1 = Db.From<Notice>(s=>s.param1 == 2);
// ...queries are more complicated but result type is same
SqlExpression<Notice> query2 = Db.From<Notice>(s=>s.param1 == 3 && s.param2 == 3);

SqlExpression<Notice> unionAll = query1.UnionAll(query2);
var result = Db.Select(unionAll);

Add OKTA as a built-in authentication provider.

Azure DocumentDB should be added among existing AutoQuery data source.

With .NET Core not initially having support for Windows Authentication using the System.Directory assemblies, I would like to request the addition of a new LDAP Authentication Provider based on the Novell.Directory.Ldap.NETStandard (https://github.com/dsbenghe/Novell.Directory.Ldap.NETStandard) project. This will allow developers to update to the latest ServiceStack while still providing a way to authenticate and authorize against a legacy/non-Azure Active Directory.

We have message-level encryption and the corresponding .Net client library to use it. But I'd love to be able to call encrypted services from JavaScript. Ideally add to ss-utils.js, or because the encryption can get bulky, into a new ss-encrypt-utils.js.

The c# SDK is seriously lagging in documentation. By that I mean IntelliSense documentation: it would be awsome with some "in line" documentation for methods and properties in the SDK