News for hackers. Stuff that matters.
Re:Every System is a Log: Avoiding coordination in distribut... by sewen on Friday January 24, 2025 @08:57AM (#42813050)
A short summary:

Complex distributed coordination and orchestration is at the root of what makes many apps brittle and prone to inconsistencies.

But we can mitigate much of complexity with a neat trick, building on the fact that every system (database, queue, state machine) is effectively a log underneath the hood. By implementing interaction with those systems as (conditional) events on a shared log, we can build amazingly robust apps.

If you have come across “Turning the Database Inside Out” (https://martin.kleppmann.com/2015/11/05/database-inside-out-...), you can think of this a bit like “Turning the Microservice Inside Out”

The post also looks at how this can be used in practice, given that our DBs and queues aren't built like this, and how to strike a sweet-spot balance between this model with its great consistency, and maintaining healthy decoupling and separation of concerns.

Re:Every System is a Log: Avoiding coordination in distribut... by teddyh on Friday January 24, 2025 @09:58AM (#42813579)
Is this summary AI generated?
Re:Every System is a Log: Avoiding coordination in distribut... by sewen on Friday January 24, 2025 @10:01AM (#42813634)
Haha, no, but maybe all the AI-generated contents out there is starting to train me to write in a similar style...
Re:Every System is a Log: Avoiding coordination in distribut... by p10jkle on Friday January 24, 2025 @10:02AM (#42813645)
I feel this happening to me too... depressing
Re:Every System is a Log: Avoiding coordination in distribut... by TeMPOraL on Friday January 24, 2025 @11:00AM (#42814380)
Or an improvement, given that SOTA models write better than most people...