What happens to a "smart" product when its cloud goes away? We start with a rare case where an EOL story did not end in a brick, then walk through the patterns that keep devices and clients useful after shutdown.
What happens to a "smart" product when its cloud goes away? We start with a rare case where an EOL story did not end in a brick, then walk through the patterns that keep devices and clients useful after shutdown.
If everything is logged, nothing is useful. Carl and Brandon walk through what logging is really for in cloud architectures, how to use log levels and structured formats without drowning in noise or cost, and the correlation, retention, and platform habits that turn logs from a line item into a debugging superpower.
Cloud networking still breaks teams in familiar ways: parity assumptions, IP and DNS drift, SNAT exhaustion, and hidden egress paths that hurt both reliability and cost. Carl and Brandon map the practical pitfalls and the architecture habits that keep multi-cloud designs predictable.
In this episode, Carl and Brandon dive deep into the world of configuration, exploring various methods for system, app, and user-facing config, including hard-coded values, configuration files, environment variables, feature flags, databases, SaaS options, DevOps patterns, and secrets management.