May 13 · 8 min read · 💡 TLDR: Polling is wasteful and can't give you true real-time delivery. Emitting events directly from application code is fragile — a partial failure leaves your database and broker out of sync. WAL-
Join discussion
Apr 20 · 19 min read · The failure scenario At 09:14:33, a customer places a £29.99 order on your platform. The order is saved to the database. The process crashes before publishing order.created to RabbitMQ. The fulfilment
Join discussion
Apr 16 · 21 min read · The failure scenario At 09:14:33, a customer places a £29.99 order on your platform. The order is saved to the database. The process crashes before publishing order.created to RabbitMQ. The fulfilment
Join discussion
Apr 14 · 10 min read · 📌 Executive Summary In a real-world setup using RabbitMQ + Celery + Docker, I encountered multiple production-level issues: SMTP credential mismatch (username & domain swapped) Environment variable
Join discussion
Apr 6 · 7 min read · Modern applications need to handle massive traffic, scale efficiently, and remain reliable under load. One of the most powerful tools used to achieve this is a queue. In this blog, we’ll break down qu
Join discussion
Apr 4 · 4 min read · But real systems don’t fail in code — they fail in communication. So I decided to build a production-style event-driven system from scratch… and break it until I truly understood it. 🧠 What I Built
Join discussion
Apr 1 · 5 min read · There's a moment when you're building a backend where you realize that not everything needs to happen immediately. A user uploads a video — do they need to wait 2 minutes for it to be transcoded befor
Join discussionMar 29 · 11 min read · Spry with Message Queues: Building Asynchronous Applications with RabbitMQ and NATS Estimated reading time: 18–25 minutes Introduction Modern applications often need to handle tasks asynchronously—whether it's processing background jobs, sending noti...
Join discussion