Loading…
Wednesday September 9, 2026 17:10 - 17:15 EDT
Hot reloading configuration in long-running services is often treated as a file-watching problem. In practice, most failures occur because configuration is mutated in place, partially applied, or insufficiently validated before entering runtime state.

This lightning talk presents a layered configuration model that makes safe hot reload a natural consequence of system design. Configuration flows through clearly separated stages: an operator-facing specification, parsing into an in-memory representation, structured validation, transformation into a runtime representation, and finally an immutable runtime snapshot used by the system.

Each stage produces a distinct representation with an explicit boundary and purpose. Validation happens before the runtime state exists. After validation, the runtime configuration is immutable and can be atomically replaced as a unit.

By separating specification from runtime and relying on immutable snapshots, hot reload becomes a matter of constructing a new validated configuration and swapping it in, rather than mutating global state. Rust’s type system and ownership model make these boundaries explicit and enforceable, reducing the risk of partial updates and inconsistent behavior.

The pattern applies broadly to long-running Rust services that need reliable configuration updates without restarts or shared mutable state.
Speakers
avatar for Ethan Hann

Ethan Hann

Independent Consultant
Ethan Hann (he/him) is a Staff Software Engineer with nearly two decades of experience building distributed systems across healthcare, ad tech, and SaaS. He has led engineering teams, architected multi-tenant platforms serving millions of users, and designed event-driven systems handling... Read More →
Wednesday September 9, 2026 17:10 - 17:15 EDT
Palais des Congrès de Montréal

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

Share Modal

Share this link via

Or copy link