MBMadhav Bhasininblog.madhav.dev·2d ago · 8 min readCloud Run Consumers and Cloud Tasks: Reactive and Delayed WorkflowsIn Day 3 we built the FastAPI producer that publishes events to Pub/Sub. Now we build what consumes them. This is where the event-driven model pays off — multiple independent services reacting to the 00
MBMadhav Bhasininblog.madhav.dev·5d ago · 7 min readFastAPI Producer: Publishing Commerce Events to Pub/SubWe have a taxonomy (Day 1) and a Pub/Sub backbone (Day 2). Now we build the service that connects them: the FastAPI ingestion service that receives commerce events, validates them, and publishes them 00
SBSamanta Bindrainarchitecturedev.hashnode.dev·6d ago · 8 min readExactly-Once Processing in ProductionWhat this article covers: how idempotency, the outbox pattern, and saga orchestration work together as a single coherent system — not three independent patterns bolted onto each other. Exactly-once p00
SBSamanta Bindrainarchitecturedev.hashnode.dev·6d ago · 7 min readDesigning a Multi-Tenant Event-Driven Platform at ScaleMost event-driven systems start with a single producer, a single topic, a single consumer. Clean. Digestible. Then you add tenants. And the question shifts from "how do we process events" to "how do w00
MYMike Younginblog.unplugit.fi·Jun 25 · 9 min readContracts Are Where Context Becomes VisibleI have started to think that we sometimes put too much attention on the inside of a bounded context, and too little on the surface where other systems meet it. The internal model matters, of course. I00
JJubsindreaded-developer.hashnode.dev·Jun 24 · 12 min readChange Data Capture & Change Tracking with Azure SQL + Azure Functions: The Hard-Earned Do's, Don'ts, and WorkaroundsIf you've ever tried to wire up Change Data Capture (CDC) or Change Tracking (CT) on Azure SQL with Azure Functions, you know the exact moment I'm talking about — that deceptively calm afternoon when 00
SBSamanta Bindrainarchitecturedev.hashnode.dev·Jun 24 · 8 min readKafka Partitioning Strategy in ProductionPartition count is the most consequential — and most irreversible — decision you make when designing a Kafka topic. Get it right and your system scales gracefully for years. Get it wrong and you're ei00
MBMadhav Bhasininblog.madhav.dev·Jun 22 · 6 min readPub/Sub Topics and Subscriptions: Designing PulseCart's Event BackboneIn Day 1 we defined PulseCart's event taxonomy — what events exist, what they mean, and what triggers them. Now we need somewhere to send them. That's Pub/Sub's job: a fully managed message broker tha00
DMDaisuke Masudaindaisuke.masuda.tokyo·Jun 22 · 20 min readApache Kafka: A Complete Engineer's Guide to Real-Time Data Streaming"Kafka is the central nervous system of a modern data architecture. Once you've seen it at scale, you can't unsee it." — An engineer who has debugged a RabbitMQ cluster at 3 AM https://speakerdeck.co00
NCN Chandra Prakash Reddyindevopstour.hashnode.dev·Jun 21 · 9 min readWhen Systems Listen: Event Driven ArchitectureTo master real-time AWS applications, focus on events rather than handling a constant stream of requests. Attending a full-day tech conference can be overwhelming with all the information you take in.00