For increasing the throughput for a specific Request service in RedisMqServer, you need to manually hardcode the number of threads that the request/service has:

https://docs.servicestack.net/redis-mq#easily-parallelize-and-multiply-your-services-throughput

Like so:
mqService.RegisterHandler<PostStatusTwitter>(ExecuteMessage, noOfThreads:2);

I would like to suggest the option to use a ThreadPool instead.

That would give the option to state the total number of concurrent/parallell processing, but there is no need to lock it down to specific requests. This is more versatile and less resource-wasting; if a certain Service isnt used right now, the threads can be used to process other Services instead.

Maybe something like:

mqService.UseThreadPool = true;
mqService.MaxNbrOfThreads = 50;

The two could be mixed, so if you'd want to dedicate some threads to a Service, then the current syntax could be used:

mqService.RegisterHandler<PostStatusTwitter>(ExecuteMessage, noOfThreads:2);

which would spawn 2 threads, and exclude this service from the ThreadPool usage.

Currently AutoQuery is coupled to OrmLiteConnectionFactory to support it's feature set.

I am able to write an IQueryDataSource to expose my data through AutoQueryData feature, however in order to use AutoQueryFeature which supports the GenerateCrudServices flag the Feature is coupled to the built in OrmLite implementation.

Would it be possible to modify it so we can use more data sources? Currently having to provide an IDbConnection forces us into SQL type languages, whereas I am trying to support CosmosDb and we should be able to support a CRUD service creation if we have some kind of Document Data Source interfaces we can implement

As it stands currently serverless is the future of application development . With services like serverless.com and the benefit these being to developers in terms of low / no touch deployments , massive cost savings and infinite scalability, it's clear that serverless is here to stay.

Many companies like us - Moosend.com - have invested years in creating microservices on Servicestack. Typically the service platform can't dictate the infrastructure architecture. Therefore now that we have decided to move a lot of our services over to AWS and Lambda we face the dilemma of having to pick between lambda and servicestack as the two are not compatible as it stands.

I vote to create a serverless.com template for a simple example on deploying a servicestack service on aws lambda. I personally spent days on trying to do this myself but without much luck. An experienced Servicestack developer can probably do this in a day or so and this will massively future proof the framework we all love so much.

Thanks
Yannis

When starting a new project one always has to build a backend environment. This includes managing users, user groups, user password changes, etc. etc. This requires a backend database and an admin front-end.

Currently, we use the ASPNETZERO framework for this purpose. https://aspnetzero.com/ But the support, documentation, and performance leave a lot of room for improvement.

We're looking to move away from ASPNETZERO as soon as we can find a replacement. Currently, their pricing starts at $1500 a year for updates and support. Something that I would gladly pay, except the documentation and support they provide is horrible.

It would also be a showcase for all of the great capabilities of ServiceStack.