Tag archive
Pub/sub decouples producers from consumers by publishing one event to a broker that fans it out to all subscribers with queues and retries. Compare direct calls vs. event-driven architecture.
A story about scaling two very different workloads independently — and the one thing that broke when...
On the previous article, we talked about client-side fetching and caching with React Query. In this...
I made a thing. In a world where prompt-to-code costs twenty bucks a month, writing about your side...
Em arquiteturas modernas baseadas em microsserviços e eventos, a comunicação assíncrona é o que...
The RabbitMQ upgrade looked like a straightforward infrastructure task: move from RabbitMQ 3.X to...
In the previous articles, we explored two pillars of event‑driven communication: Fire‑and‑forget...
The event-XOR-error invariant on command handlers. How to inform the caller of a business outcome without breaking the event/error separation, and why audit logging must be atomic.
Um 02:13 Uhr kam von einem Kollegen aus einem benachbarten Fintech Team die Nachricht, die man...
Das erste event-driven System fühlt sich wie Magie an: eine Datei landet im Bucket, eine Function...
At 02:13 a.m., a colleague from a nearby fintech team sent the kind of message nobody wants during a...
In the first two articles, we saw how an event bus can completely decouple components for one‑way...