> It's got a maximum size cap, It's ok, it's a kv store. > is trivially introspectable by via any process that can read `/proc`, It's ok, containerized apps

> It's got a maximum size cap, It's ok, it's a kv store. > is trivially introspectable by via any process that can read `/proc`, It's ok, containerized apps are expected to run in isolated environments where you are the only one with access to this info. > and sucks at representing hierarchical or structured data beyond k=v. It's ok, it's a KV store. If it isn't, you are doing something terribly wrong. Virtually all config systems developed in the past decade follow this pattern, where multiple config providers are applied hierarchically and env vars are the last chain in the chain of responsibility that overrides all other providers. It works well.