News for hackers. Stuff that matters.
Re:Microservices Circuit-Breaker Pattern Implementation: Ist... by sagichmal on Thursday December 13, 2018 @05:17PM (#18676642)
It is almost never better to use async communication between services. The failure modes are strictly more, and finding and fixing problems is substantially harder.

https://programmingisterrible.com/post/162346490883/how-do-y...

Re:Microservices Circuit-Breaker Pattern Implementation: Ist... by discreteevent on Thursday December 13, 2018 @06:10PM (#18676992)
Part of that article seems to be saying: I don't see any point in having suspension in vehicles. When I overload my truck it handles like shit.
Re:Microservices Circuit-Breaker Pattern Implementation: Ist... by SuddsMcDuff on Saturday December 15, 2018 @11:44PM (#18691774)
Are you basing that on personal experience, or just on that blog post?
Re:Microservices Circuit-Breaker Pattern Implementation: Ist... by sagichmal on Tuesday December 18, 2018 @10:27PM (#18712781)
The blog post elegantly reflects my own experiences.
Re:Microservices Circuit-Breaker Pattern Implementation: Ist... by SuddsMcDuff on Monday December 31, 2018 @09:03AM (#18794499)
I found the blog post to be awful, the rationalization of a man stuck in a particular mindset who failed to adapt to a new paradigm. The line "You have publish-subscribe, but you really want request-response." says it all. He simply cannot imagine a software design which doesn't depend on synchronous request/response.