Hacker News Reader

Product description says:

a HTTP reverse proxy built in Rust, that can handle fine grained configuration changes at runtime without reloads, and designed to never ever stop.

How is that immutable? Sounds like it is highly mutable by design.

View on HN

Because the backend servers/containers/pods are immutable, every deployment creates new backends (that have new IPs) and then kills the old backends. This requires changing the proxy config at runtime. In the old days the backends would be mutable and would be updated in-place, keeping their IPs, so you could leave the proxy config alone.

I'm sure the OP understood. But there is fine irony in the fact that a product that sells itself as immutable infrastructure is highly mutable.

Is it irony? Immutable data structures in languages like Haskell work the same way, copies are made and then the older ones are garbage collected. Seems like the same definition applies here.

Immutable doesn’t mean it cannot be updated. It just means that updates are happening without touching the same copy. This CoW-ish style is what they’re selling.

Reply on news.ycombinator.com