News for hackers. Stuff that matters.
Re: by hakunin on Wednesday August 30, 2023 @06:39PM (#37330084)
In most cases microservices are an anti-pattern, because they are trying to solve problems that can be solved without incurring their complexity and sacrifices.

However, I remember Sagas originally applied to dealing with multiple 3rd party API, the example was "book flight, hotel, rental car". If you're dealing with necessarily separate systems, then there's probably a place for sagas.

Re: by nextaccountic on Wednesday August 30, 2023 @07:40PM (#37330566)
The author talks about this too

> As soon as we start doing separation of domains according to data governance, we may quickly realize that in the vast majority of cases, microservices look a lot like traditional monoliths and the domain they should handle is big. Or realize that traditional monoliths are, in fact, microservices. This happens because most organizations have only a very limited number of truly independent domains. Most often — one.