architecture
architecture
ruby
When you should NOT use messaging, or how not to make things harder for yourself
Messaging is not a default answer. When a business flow is synchronous, queues add complexity without value and message ordering becomes your biggest pitfall. How to recognise the cases where a simple synchronous call keeps the system easier to build and debug.
rabbitmq
Coupling issues in distributed systems
Coupling in distributed systems goes far beyond shared code: technology, location, semantic, data format, conversation, topology, order, and temporal coupling each hurt resilience differently. What every type looks like and how to keep services independent.