subes
commented
4 years ago https://github.com/resilience4j/resilience4j
seems to be a more active library where this adaptive concurrency limit is either also available or could be added to
Open subes opened 4 years ago
subes
commented
4 years ago https://github.com/resilience4j/resilience4j
seems to be a more active library where this adaptive concurrency limit is either also available or could be added to
subes
commented
4 years ago Another alternative:
subes
commented
4 years ago Some info on current options: https://github.com/spring-petclinic/spring-petclinic-microservices/issues/117
https://github.com/Netflix/ribbon
https://github.com/spring-cloud/spring-cloud-circuitbreaker might be the right API to abstract the other options
Though spring-retry has a CircuitBreakerRetryPolicy which could be used directly with the existing @Retry annotations. No need to use resilience4j or such.
Though something smarter like concurrency-limits would still be interesting.
https://github.com/Netflix/concurrency-limits
Though other implementations should be looked into since netflix abandoned the project. But the concept looks promising for REST-Clients. Though we could also switch to gRPC if the performance is good enough with that (but the solution should with any transport). Would be most interesting in the financial data services.
Though not needed right now because we are not at that scale with the infrastructure, rather a reminder for a later time.