Category
Software architecture in backend development is about the patterns that shape how services communicate, share data and handle failure. Common choices include request-response or event-driven messaging with brokers such as Kafka and RabbitMQ, CQRS and event sourcing, sagas for distributed transactions and resilience patterns like circuit breakers, retries and bulkheads. Each pattern solves a specific problem and adds its own complexity, so the trade-offs matter more than the names.
8 articles
Monolith vs microservices decided honestly: the side-by-side comparison on team shapes, scaling, and operational maturity, the modular monolith middle path, and when to use microservices because…
How Kafka works from the log out: topics and partitions as the units of order and parallelism, consumer…
Kafka vs RabbitMQ decided on model shape, not brand: the durable log versus classic routing, when to use…
The circuit breaker pattern: the three circuit breaker states, failing fast with real fallbacks, and the bulkhead pattern…
Service discovery: how the service registry tracks who is up, the client-side vs server-side discovery comparison, and the…
Event driven architecture: the pub/sub vs message queue comparison, event sourcing as the system of record, and choreography…
Message queues in system design: the at-least-once vs exactly-once delivery comparison, message ordering, and the dead letter queue…
Microservices architecture explained: service boundaries and bounded contexts, the microservices trade-offs in both directions, and honest guidance on…
