Feature Requests
Feature, docs and use-case samples requests for ServiceStack. If you can, focus on the end-user benefit / use-case, rather than the technical details so we can focus on the end-goal and free us to work on how best to achieve it. Features can also include supporting content, e.g. a starter project on how to use ServiceStack with another product (e.g. SS + SharePoint).
-
support cockroach db for GenerateCrudServices
support cockroach db for GenerateCrudServices
3 votes -
KeyDb-Redis Support (A Multithreaded Fork of Redis That’s 5X Faster Than Redis)
KeyDB is a Faster, Drop-In Alternative to Redis
KeyDB maintains full compatibility with Redis modules, API and protocol.
Seamlessly drop in KeyDB and maintain full compatibility with your existing clients, scripts and configurations.I assume because KeyDb is billed as a "drop-in" replacement that this would be low hanging fruit to get ServiceStack.Redis to support Redis-KeyDb
3 votes -
Show user API Key from Studio App
Would be nice to see the user's associated api keys from the Studio App when you are logged as an admin.
1 vote -
Support certificate-based authentication to Redis servers.
Redis supports a certificate-based authentication scheme as well as the legacy password and more recent user + password schemes. Cloud providers such as RedisLabs as well as self-hosted and Docker-based Redis servers also support this method of authentication.
This should be added to ServiceStack so the full range of authentication schemes are supported.
Thanks.
2 votes -
support dapr for MQ Messaging
For example, if you use MQ message, consider supporting dapr.
3 votes -
Use a ThreadPool for RedisMqServer Services instead of hardcoding nbr of threads
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;…
3 votesUsage of a dedicated thread per Message Type is per design so throughput can be controlled per Type, sequential processing can be enforced and processing is isolated from long tail of other lower priority MQ Messages delaying processing of higher priority ones.
You can reduce number of sleeping threads by having fewer MQ Types, i.e. combining multiple MQ Tasks into a single union type whose Service implementation can delegate into invoking their different individual services.
Mixing Threadpool MQ Server strategies will not happen with the existing implementation, it requires a completely new implementation with different behavior & design goals.
I’ll leave this feature request open in-case anyone decides to implement a different MQ Server strategy and can post a link to their implementation here.
-
Postman v2 format support
right now, you cannot import postman metadata exposed by SS into the latest version of Postman because its complaining about v1 schema and conversion requires an insane amount of npm garbage to be installed.
any chance of adding v2 postman metadata, or links to v1 and 2?
6 votespostman2 support is currently available as a mix in:
https://docs.servicestack.net/releases/v5.11#postman-v2-collections
Please report any issues, we’ll look at eventually replacing the existing postman support in ServiceStack in the near future.
-
Python as a supported Native Type
The addition of Python as a Native Type would make it a lot easier to integrate ServiceStack and Python.
3 votes -
Support JSV serialization in request URL for typescript client
SS supports deserializing nested request objects if they are sent in URL as JSV. The typescript client should support this when sending a request object that has a nested object. At the moment it just appends the word "Object" to URL. I think if it doesn't support it then it should generate an error/warning when detecting a nested object as would save some confusion.
1 vote -
1 vote
-
Support AbortController API in servicestack-client
Allow a signal to be passed in when making requests via the client side lib servicestack-client.
11 votes -
Decouple AutoQuery from OrmLiteConnectionFactory
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…
3 votes -
Make servicestack compatible with AWS lambda
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…
1 vote -
Update aurelia-spa to use authentication like angular-spa and other templates
This would be super helpful to have the current Aurelia template updated with the authentication piece that has been added to the angular and react spa templates.
1 vote -
Implements IDistributedCache on ServiceStack caching providers
It would be very useful to have the implementation of .net core IDistribuitedCache interface on ServiceStack caching providers. This would improve the integration with other modules that support the standard .net cache interface.
References:
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-3.1
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/distributed?view=aspnetcore-3.12 votes -
Support postgresql @@ operator OrmLite
Currently the PostgreSQL text match operator @@ throws validation error when used in a Ormlite custom query string.
Would be nice to get support for that and also support for parameterised query to support tsquery type.
1 vote -
Support for new ACL feature of redis
redis 6.0.6 supports ACL. ACL is powerfull and secure, which user can write, which user can only read. What wildcard keys can be read...
Current version of ServiceStack allows password but not a specified username.
AUTH password -> AUTH username password3 votes -
MessageService with Kafka same as current RabbitMQ integration
Is this something that could be done? Would bring powerful streaming to ServiceStack
2 votes -
ORMLite support for TimescaleDB
Maybe this is easy to do, as TimescaleDB is an extension to PostgreSQL.
1 vote -
Memcached for .Net Core
Could we add a .Net Core version of ServiceStack.Caching.Memcached? The derived library has been updated here
2 votes
- Don't see your idea?