5 ms·

Microservices Circuit-Breaker Pattern Implementation: Istio vs. Hystrix

86 points by nfrankel 8y ago

sgt 8y ago
Also worth reading: https://vertx.io/docs/vertx-circuit-breaker/java/ https://vertx.io/docs/vertx-circuit-breaker/java/
- dlojudice 8y ago
  And this: Pattern: Service Mesh - http://philcalcado.com/2017/08/03/pattern_service_mesh.html http://philcalcado.com/2017/08/03/pattern_service_mesh.html
Daishiman 8y ago
These microservice design patterns bring back horrible memories of the design overarchitecture that was in vogue back in the J2EE years, where you basically need patterns to deal with the issues your new patterns bring up. Of course in practice most reasonable people choose to deal with these things by dealing with complex failures in the most simple way, but the proliferation of these "solutions" IMO bring in more trouble than it could be possibly worth.
bpicolo 8y ago
Hystrix is in maintenance mode - README says Netflix is moving towards e.g. https://github.com/resilience4j/resilience4j https://github.com/resilience4j/resilience4j > Netflix Hystrix is now officially in maintenance mode, with the following expectations to the greater community: Netflix will no longer actively review issues, merge pull-requests, and release new versions of Hystrix.
- ramchip 8y ago
  It’s mentioned in the article: > Netflix has recently announced it has stopped development of the Hystrix library in favor of the less well-known Resilience4J project. > Even if the client code might be a bit different, the approach between Hystrix and Resilience4J is similar.
SuddsMcDuff 8y ago
Usually better to use asynchronous communication between services.
- discreteevent 8y ago
  With a good old fashioned message broker for guaranteed eventual delivery, decoupling, discovery and elasticity (if you can fit it in to your setup)
  - sigmonsays 8y ago
    I can't tell if this is a joke or not.
    - discreteevent 8y ago
      I'm not joking. Just to be clear, I'm taking asynchronous to mean a call that is not transactional. Where you are ok with eventual consistency. If something is transactional then keep it in one service. Make it an action not a transaction and save yourself a lot of grief. So if something is asynchronous then why not back it up with a message broker and get the properties I listed (in earnest).
      - SuddsMcDuff 8y ago
        I'd be interested to know if anyone's had success with distributed transactions in a microservice architecture. I've gotten into a world of pain every time I've tried. We did have some success at one of my previous companies (wiggle.co.uk), but that was mainly due to pretty tight integration between MSMQ, MSDTC and MS Sql Server. Even then, we tried to avoid distributed transactions as much as possible.
- bni 8y ago
  On its own this is a worthless hand wavy statement. How do you accomplish this when you have a synchronous client (ie a user waiting in his web browser)? Should the browser poll for the result? How could you possibly implement something like this in the real world?
voycey 8y ago
That cookie notification is absolutely atrocious - is there really any need for a full screen popover??

86 points by nfrankel 8y ago

sgt 8y ago

Also worth reading: https://vertx.io/docs/vertx-circuit-breaker/java/ https://vertx.io/docs/vertx-circuit-breaker/java/

dlojudice 8y ago
And this: Pattern: Service Mesh - http://philcalcado.com/2017/08/03/pattern_service_mesh.html http://philcalcado.com/2017/08/03/pattern_service_mesh.html

Daishiman 8y ago

These microservice design patterns bring back horrible memories of the design overarchitecture that was in vogue back in the J2EE years, where you basically need patterns to deal with the issues your new patterns bring up. Of course in practice most reasonable people choose to deal with these things by dealing with complex failures in the most simple way, but the proliferation of these "solutions" IMO bring in more trouble than it could be possibly worth.

bpicolo 8y ago

Hystrix is in maintenance mode - README says Netflix is moving towards e.g. https://github.com/resilience4j/resilience4j https://github.com/resilience4j/resilience4j > Netflix Hystrix is now officially in maintenance mode, with the following expectations to the greater community: Netflix will no longer actively review issues, merge pull-requests, and release new versions of Hystrix.

ramchip 8y ago
It’s mentioned in the article: > Netflix has recently announced it has stopped development of the Hystrix library in favor of the less well-known Resilience4J project. > Even if the client code might be a bit different, the approach between Hystrix and Resilience4J is similar.

SuddsMcDuff 8y ago

Usually better to use asynchronous communication between services.

discreteevent 8y ago
With a good old fashioned message broker for guaranteed eventual delivery, decoupling, discovery and elasticity (if you can fit it in to your setup)
- sigmonsays 8y ago
  I can't tell if this is a joke or not.
  - discreteevent 8y ago
    I'm not joking. Just to be clear, I'm taking asynchronous to mean a call that is not transactional. Where you are ok with eventual consistency. If something is transactional then keep it in one service. Make it an action not a transaction and save yourself a lot of grief. So if something is asynchronous then why not back it up with a message broker and get the properties I listed (in earnest).
    - SuddsMcDuff 8y ago
      I'd be interested to know if anyone's had success with distributed transactions in a microservice architecture. I've gotten into a world of pain every time I've tried. We did have some success at one of my previous companies (wiggle.co.uk), but that was mainly due to pretty tight integration between MSMQ, MSDTC and MS Sql Server. Even then, we tried to avoid distributed transactions as much as possible.
bni 8y ago
On its own this is a worthless hand wavy statement. How do you accomplish this when you have a synchronous client (ie a user waiting in his web browser)? Should the browser poll for the result? How could you possibly implement something like this in the real world?

voycey 8y ago

That cookie notification is absolutely atrocious - is there really any need for a full screen popover??