State of Emergency: Effective Exception Handling in a Distributed Architecture
summary
Presents a practical approach used at EOS TS for consistent exception handling across a highly distributed Java/Spring microservices architecture. Covers designing exception handling at the macro-architecture level to integrate logging, distributed tracing and metrics, and shows automated tooling to enforce team conventions. Aims to help teams provide uniform error information to users, support staff and neighboring systems.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:11Project context
- 3:55Why exception handling matters
- 5:21Java exceptions basics
- 7:51Exception facade
- 10:59Spring exception strategies
- 12:06Metadata for distributed systems
- 17:01Logging and tracing
- 19:09Anti-patterns and scalability
- 21:57Circuit breakers
- 23:46Recoverable errors and retries
- 24:52Messaging error handling
- 27:48Disaster recovery with Kafka
- 29:12Governance and shared libraries
- 31:41Enforcing rules with SonarQube
- 32:47Q&A
related talks
47mSilence is Coming: Surviving Chaos in a Distributed Event-Driven Architecture
29mThe art of being resilient. How to handle failures gracefully in Distributed Systems.
46mThe Do's and Don'ts of Error Handling
45mDo Distributed Systems they said. It'll be fun they said.
50mCommunication in a Distributed World
51mComplex Event Flows in Distributed Systems
24mEngineering Real-Time Data Synchronization Across Multi-Cloud Systems
29mPractical distributed systems: Building for the real world with chaos engineering