Do Distributed Systems, they said. It'll be fun, they said
summary
Practical rundown of building a distributed messaging platform: explains why Axon Server and a pluggable message bus let a monolith evolve without rewriting business logic, and shows engineering tradeoffs — retry vs duplicate delivery, idempotent commands vs compare-and-swap, timeouts with the saga pattern, chaining or consistent hashing to preserve order, and switching to streaming to fix latency. Examples come from AxonIQ’s experience with deployments and a working approach to swap implementations without changing domain code.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:20Microservices communication
- 3:47Message dispatching basics
- 7:38Messages not delivered
- 11:02Duplicate message handling
- 15:31Out-of-order messages
- 20:31Infrastructure changes
- 26:08Performance with streaming
- 28:25Takeaways and conclusion
related talks
50mDo Distributed Systems they said. It'll be fun
45mDo Distributed Systems they said. It'll be fun they said.
58mElements of Distributed Architectures
44mDistributed journey
01h 00mChallenges of distributed systems
57mSafe Passage: Messaging in a distributed systems environment
01h 02mCommunication Patterns for Distributed Architectures
44mDistributed systems and scalability rules