New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Managing Resource Pools #94

Open

billoneil opened this issue Jan 6, 2019 · 0 comments

Labels

Contributor

billoneil commented Jan 6, 2019

Similar to Managing timeouts we might want the ability to customize the resources for given actions to prevent critical path code from failing.

Limit the number of connections per endpoint. If you have some long-running operations consider queuing up connections instead of flooding the server with long running operations. If the connection pool is shared with higher throughput and lower latency endpoints you could block critical path code if too many long-running connections are being processed.
Multiple connection pools (HTTP, JDBC) same as above but for other types of resources.

billoneil mentioned this issue

Achieving many of the microservice benefits in a monolith #96

Open

4 tasks

billoneil added the Proposed Topic label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment