Supervisor Bridges & Mixed Process Hierarchies
Integrate non-OTP processes and external subsystems into your supervision tree using supervisor_bridge, keeping fault tolerance intact.
Why a Supervisor Bridge?
Not every process you depend on is a clean OTP gen_server. Sometimes you must supervise a plain Erlang process, a port, or a third-party subsystem. The supervisor_bridge behaviour lets such a process appear as a normal child in a supervision tree.
The Problem It Solves
A standard supervisor only knows how to start, stop and restart OTP-compliant children. A raw process started with spawn_link does not respond to OTP shutdown protocols. The bridge translates between the two worlds.
All lessons in this course
- Complex Supervision Trees
- Dynamic Process Management
- Advanced Restart Strategies
- Supervisor Bridges & Mixed Process Hierarchies