Xe 
Winter Jo 
❄️@cadey you could replace most of this with actual terms used with micro services and it would look even more unhinged; https://microservices.io/patterns/data/saga.html
Robin Syl 🌸
@ShadowJonathan @cadey I don't like this
Sören@ShadowJonathan @cadey “If a local transaction fails because it violates a business rule then the saga executes a series of compensating transactions that undo the changes that were made by the preceding local transactions.” What could possibly go wrong
@ShadowJonathan @chucker just don't let them be offline
Sir Dippingsauce@chucker @ShadowJonathan @cadey This reminds me of the early days of J2EE where complex patterns were "supported" by even more complex patterns to compensate for arguably bad practices. You literally had to read 3 doctoral essays to write a trivial pet store webapp.
iliana@cadey hi good morning did you make this or know who did because i would like to credit it properly for an internal doc at work
@iliana @danderson would know
Dave Anderson@cadey @iliana alas my provenance trail ends at "posted yesterday in a private discord". Search suggests https://www.reddit.com/r/ProgrammerHumor/comments/10vdxff/microservices/ may be the source, 24d ago, but I'm not certain.
Teirm@cadey So for system design interviews the answer is always 'monolith'?
Yulian Kuncheff@cadey This reminds me of this article I read recently: http://blogs.newardassociates.com/blog/2023/you-want-modules-not-microservices.html