Derek Comartin

Random reminder that I have a YouTube channel where I post videos about software architecture and design. Usually in the 10 min range trying be concise as possible. If you enjoy please share. Have suggestions? Please let me know. @codeopinion" target="_blank" rel="nofollow noopener">youtube.com/@codeopinion

Friendly reminder: I have a YouTube channel that is 30 subscribers away from the useless 100k-subscriber vanity metric. @CodeOpinion" target="_blank" rel="nofollow noopener">youtube.com/@CodeOpinion

Full Post: codeopinion.com/why-sagas-feel…

A Saga coordinates a process. Reconciliation corrects drift. It's not a cleanup job and it's not replacement for Sagas, but as a safety net around them. Use the Saga to move the workflow forward. Use reconciliation to ask "What should be true, what is actually true, and how do we safely correct if needed?”

@omardelrio If have to think how to qualify when it's appropriate. That's actually a good video topic

@codeopinion IMO, EDA is something everyone thinks they need, but only a few really do. Maybe the architectural concepts are more widely applicable, but people go wild with just frameworks and tech because that's what they like to do.

"We switched to event-driven architecture. Now we can’t debug anything." The problem usually isn’t event-driven architecture. It’s treating everything as an event, making everything async, losing visibility, and confusing commands with events. EDA isn’t your whole architecture. It’s one part of it. Use the right communication style for the outcome you need. codeopinion.com/debugging-even…

Fairly certain Koodo's (cell provider in Canada) portal runs on a 486 connected to a 14.4k modem.

Welcome to the world of frontend web development.

@erichydrick I endorse it again 😂

I wholeheartedly endorse this @codeopinion take:

Probably should roll your own DB while you're at it.

In complex systems (and complicated projects are such systems) almost-always something breaks in a way that you did not expect (even in your most fastidious threat-models, contingency-plans, etc.) There simply are too many possibilities for adverse events; too many failure-modes.

@yordisprieto Looks good. I'd add something about ownership/authority.

@codeopinion any changes here?

A system is what the system does yordisprieto.com/the-system-is-… #systemdesign #softwarearchitecture #systemthinking

I'm not saying don't use you're DB as a queue but you need to realize all the patterns you're about to implement to make it behave like one. Also, if immediately think of Kafka or redis first of you need a queue, that's like thinking of an excel file when you need a database.

Kafka is a distributed log Redis/Postgres are data stores None of these are “just queues”. You’re adding the semantics and patterns on top to (somewhat) behave like a queue That matters because the trade-offs are very different.

Seems like people think "good architecture" means adding layers, interfaces, and abstractions everywhere. But a lot of the time, that’s just an upfront tax on delivery. If I have one ProcessPayment handler, one Stripe integration, and one place where it’s used… why am I also creating an IPaymentService just to wrap it? That extra indirection doesn’t magically make the system more flexible. If anything, it often makes change slower. The slice is already the boundary! Pragmatic architecture isn’t about avoiding all coupling or following every pattern. It’s about keeping dependencies contained, organizing around change, and not paying for flexibility you don’t actually need yet.

Longer version: codeopinion.com/is-event-drive…

The term "event-driven architecture" has a lot of people confused. Events as state or events as notifications. I see these two concepts lumped together all the time, but mixing them up is a shortcut to architectural turd pile. Event sourcing uses events as the source of truth which you can derive state from. Notifications use events to let other parts of the system react to something that already happened. Same concept on the surface, very different design purpose underneath. And when those two get lumped together, it creates a lot of confusion about when each approach actually makes sense.

My timeline loves people who feel strongly against Garry Tan.