What does HackerNews think of Hystrix?

Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.

Language: Java

Ask HN: Modern Node.js Request Fault Tolerance Library? | May 2023
Oops, forgot to include the Hystrix link, https://github.com/Netflix/Hystrix
Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region | Dec 2021
Expand Context ↕
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 - https://www.youtube.com/watch?v=CZ3wIuvmHeM I think talks about Hystrix a bit, but I'm not sure if it's the presentation I'm thinking of from years ago or not.
Ask HN: What are the best publicly available FAMANG code repos? | Aug 2021
Expand Context ↕
Thank you for sharing! Will take a look at Titus - it seems to be split into three - API, Control Plane and Executor.

For anyone wanting to take a look:

https://github.com/Netflix/eureka

https://github.com/Netflix/Hystrix

https://netflix.github.io/titus/

https://github.com/Netflix/titus-api-definitions

https://github.com/Netflix/titus-control-plane

https://github.com/Netflix/titus-executor
A self-killing web site requested by a customer (2011) | May 2020
Expand Context ↕
While not actively developing infrastructure myself, I've always like the concept presented in the Hystrix package: https://github.com/Netflix/Hystrix

Even though it seems it is no longer maintained, the circuit breakers, fail over modes and all that are well documented.

And I don't know why Hystrix hasn't been adopted by a wide audience yet. It seems like a necessity in the micro service landscape.
Concurrency Limits by Netflix | Mar 2018
This library looks very interesting. I've used a similar approach for pulling batches of items from a queue (e.g. discover the optimal batch size and inter-poll wait time). There are plenty of other places we could benefit from something like this. I can't wait to try this out.

Netflix puts out some amazing Java libraries. I've had excellent results using Hystrix [0]. It has been an excellent addition to our systems.

[0] https://github.com/Netflix/Hystrix

Failsafe – failure handling with retries, circuit breakers and fallbacks | Jul 2016
How is this distinct from Hystrix (https://github.com/Netflix/Hystrix)? Why should I use one over the other?
Matrix of Services | Jun 2014
Expand Context ↕
You'll want to issue requests concurrently, use timeouts liberally, and implement fallbacks to cached/calculated data in the event that one of the services fails or misbehaves. Those are just a few guiding principles that will help when building a SOA (service-oriented architecture). Netflix has a great blog post on the structure of their platform [1]. They even open-sourced Hystrix [2], the library they use internally.

[1] http://techblog.netflix.com/2012/02/fault-tolerance-in-high-...

[2] https://github.com/Netflix/Hystrix
Principles of Software Engineering, Part 1 | Apr 2013
Expand Context ↕
Unit tests are of course important, but they don't test for higher level failures like network issues, high latency, increased load, etc. Your components must be designed to be isolated from incidents as much as possible, possibly using the techniques implemented in Hystrix [1], an open source library from Netflix.

[1] https://github.com/Netflix/Hystrix
Joe Armstrong: Solving the wrong problem | Mar 2013
Expand Context ↕
So somebody else doesn't waste a minute or two googling up the wrong tree: It's Hystrix, not Hysterix.

https://github.com/Netflix/Hystrix

http://akka.io/