Revealing Resilience Vulnerabilities in Spring Boot Architectures
summary
A reproducible chaos gameday framework tests Spring Boot resilience by injecting faults into a three‑service setup (order, customer, product) registered with Eureka and protected by circuit breaker with Hystrix. The team automates experiments and cloud deployment (Azure via Pulumi/CLI) and uses Chaos Monkey for Spring Boot to run attacks such as a 50s injected latency against customer service to verify timeouts and fallbacks, observe cascading behavior, and record whether circuit breakers and bulkheads actually prevent system collapse.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker
- 1:21Understanding resilience
- 4:02Real-world failures
- 6:44Anti-patterns and solutions
- 11:07Principles of chaos engineering
- 14:33Framework for game days
- 17:43Demo and implementation
related talks
52mChaos Engineering with Spring Boot
49mChaos Engineering: Withstanding Turbulent Conditions in Production
39mResilience & Chaos Engineering in the Cloud
30mChaos Monkey for Spring Boot
33mChaos Monkey for Spring Boot
29mEngineering Chaos for Resilient Applications: A Gameday Guide
26mBreaking Systems for Resilience
57mChaos Engineering Primer
