java-microservice VS Hystrix

Back in 2017, I was solving many of those distributed-systems challenges using Spring Cloud with Netflix OSS; you can check out my Bootstrapping microservice project here. But Netflix OSS is for Java developers mostly and microservices can be implemented in a variety of frameworks/languages, so we should be able to handle those challenges outside the application level.

I have two relevant opensource projects related to microservices(Java microservices and Service mesh) with thousands of access, and I have been working with this architecture for a few years; however, I don't recommend microservices architecture for most cases.

Oops, forgot to include the Hystrix link, https://github.com/Netflix/Hystrix

They had to figure out video compression that worked at the volume that they wanted to deliver. They had to build and maintain their own CDN to be able to have a always available and consistent viewing experience. Don’t even get me started on the resiliency tools like hystrix that they were kind enough to open source. I mean, they have their own fucking data science framework and they’re looking into using neural networks to downscale video.. Sound familiar? That’s cause that’s practically the same thing as Nvidia’s DLSS (which upscales instead of downscales).

When breaking up a monolithic app into microservices, the communication between these services becomes vital to the health and performance of the application. Technically, you could incorporate the features to manage this traffic directly into your application. This is what Twitter, Google, and Netflix did with massive internal libraries like Finagle, Stubby, and Hysterix.

Hystrix: https://github.com/Netflix/Hystrix Hollow: https://hollow.how/

Have you actually read the article and maybe also https://github.com/Netflix/Hystrix status section??!

I came upon Resilience4J when I was running my talk on the Circuit Breaker pattern. The talk included a demo, and it relied on Hystrix. One day, I wanted to update the demo to the latest Hystrix version and noticed that maintainers had deprecated it in favor of Resilience4J.

Netflix was talking alot about circuit breaks a few years ago, and had the Hystrix project. Looks like Hystrix is discontinued, so I'm not sure if there are good library solutions that are easy to adopt. Overall I don't see it getting talked about that frequently... beyond just exponential backoff inside a retry loop.

- https://github.com/Netflix/Hystrix