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 didn't find support of client side sharding with sentinels in your Redis API. It will be a nice to have feature. I asked this question on stackoverflow, if you have some solution for the problem, it would be great to hear: https://stackoverflow.com/questions/50107173/servicestack-redis-is-sharding-supported-in-sentinel-mode

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

Support Condition Expressions for PutItem, UpdateItem and DeleteItem operations.

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

The ServiceStack Stripe library currently doesn't support retrieving of Stripe Events. It would be nice to have this feature especially when working with webhooks.

As it currently stands, I either have to install both the Stripe.net and ServiceStack.Stripe packages in my project, or switch to using just the Stripe.net package.

ADOMD.net Cubes as a source of data. I think this would be huge in adding a provider to the mix and utilize Analysis Service cubes to return faster data/query's for warehouse service use.

Some older release notes https://github.com/ServiceStack/ServiceStack/blob/net40/docs/2015/release-notes.md states that Mini Profiler async support is there, but unless I am missing something, using v5.0, I cannot get it to work. Looking at ProfiledCommand, it does not actually overload the async overloads and call IDbProfiler methods.

MiniProfiler integrated this last februari: https://github.com/MiniProfiler/dotnet/commit/8973afb7bd418a37ce38e0805dc3636942ea7788

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

http://docs.servicestack.net/kotlin-add-servicestack-reference should be updated to reflect the fact that Google now provides first class support for Kotlin in the IDE

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

Look at adopting approach for custom impl at:
https://github.com/ServiceStack/ServiceStack.Java/issues/20

The mongo driver is available on .net core but needs a nuget spec for it.

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.

I was just reading about the Redis Labs new RediSearch product for use in implementing a search engine in Redis. I saw in the RediSearch product page that StackExchange has a C# client for this product. Do you plan to implement RediSearch client in ServiceStack.Redis? I prefer ServiceStack modules to StackExchange.

If this is your roadmap, can you project delivery of such a client?

Keep up the good work! Thanks!

By default the metadata page could group the operations by the service they are in.
All user operations under UserService.
Order operations under OrderService.
etc.

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

Add OKTA as a built-in authentication provider.

The API request logger logs all fields and there is now way to disable any of them. Specifically, logging the users cookie each time takes up a huge amount of space and also makes the display difficult to use. Please add a config option to allow control over which fields get logged.