Building Resilient Systems with Stacking
summary
A concrete boot strategy that turns failures into manageable states: build releases with distillery, read system config before the VM, start a config gen_server that halts boot if required values fail to load, start external connectors in disconnected mode and reconnect with backoff and jitter, use a watchdog that sets and clears alarms via alarm_handler (hysteresis: wait for three good checks), use a circuit breaker like Fuse and a write‑through ETS cache (Vapor tooling available) to keep services resilient.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:34BREAKING RESILIENT
- 0:45IS STACKING MY APPLICATION?
- 0:56HOW TO BOOT YOUR APPS CORRECTLY
- 4:29SYSTEMS HAVE DEPENDENCIES
- 6:24SCALING IS A PROBLEM OF HANDLING FAILURE
- 9:35STACKED DESIGN
- 9:51LETS TALK ABOUT.. BOOTING THE RUNTIME & CONFIGURATION STARTING DEPENDENCIES CONNECTING TO EXTERNAL SYSTEMS ALARMS AND FEEDBACK COMMUNICATING WITH SERVICES WE DON'T CONTROL
- 10:55OF DEPLOYMENT IN ERLANG/ELIXIR
- 11:29WHAT HAS TO BE HERE TO START OUR APPLICATION?
- 16:23LETS TALK ABOUT... BOUTINO THE RUNTIME & CONFIGURATION STARTING DEPENDENCIES CONNECTING TO EXTERNAL SYSTEMS ALARMS AND FEEDBACK COMMUNICATING WITH SERVICES WE DON'T CONTROL
- 17:12SUPERVISORS ARE ABOUT GUARANTEES
- 26:46CIRCUIT BREAKERS
- 27:25ADDITIVE INCREASE MULTIPLICATIVE DECREASE
- 27:46LETS TALK ABOUT... BOOTING THE RUNTIME & CONFIGURATION STARTING DEPENDENCIES CONNECTING TO EXTERNAL SYSTEMS ALARMS AND FEEDBACK COMMUNICATING WITH SERVICES WE DON'T CONTROL
- 28:09SYSTEMS SHOULD... HANDLE FAILURES GRACEFULLY PROVIDE FEEDBACK TO OTHER SYSTEMS GIVE INSIGHT TO OPERATORS
related talks
45mThe simplest way to build resilient applications
55mGoing Resilient
57mResilience by Design
37mResilience Design Patterns
51mPatterns for building resilient software systems
35mDesign patterns for application resiliency
28mRevealing Resilience Vulnerabilities in Spring Boot Architectures
29mResilient by Design