Skip to content
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

Reactive Programming - resilience4j #311

Open
matiwinnetou opened this issue Mar 5, 2025 · 1 comment
Open

Reactive Programming - resilience4j #311

matiwinnetou opened this issue Mar 5, 2025 · 1 comment
Labels
Make Robust Non Functional Requirement Performance Improvement

Comments

@matiwinnetou
Copy link
Collaborator

matiwinnetou commented Mar 5, 2025 •
edited
Loading

This product is used by exchanges with sometimes massive traffic / load and number of concurrent users, one performance issue somewhere can cripple instance completely. For this we have reactive programming and circuit breakers / bulkd heading. Introduce resilience4j to the project for high concurrent users scenarios to protect the instance and not cause cascading failures.

Ideally we should make it an optional configuration parameter since some exchanges DO NOT HAVE ability to run reactive sidecars.
@matiwinnetou
Copy link
Collaborator Author

For now exchanges can use sidecard pattern and protect each db endpoint with a circuit breaker and do rate limiting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Make Robust Non Functional Requirement Performance Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matiwinnetou