Sidecars were meant to isolate concerns and standardize infrastructure. Instead, many teams end up managing a growing fleet of proxies, daemons, and coordination glue that quietly slows everything down.

In this episode, we uncover the sidecar trap—how a well-intentioned pattern can balloon into operational drag, and what happens when the architecture starts optimizing for the infrastructure, not the app. Roberto Bianchi, Staff Engineer at Spendesk, joins us to share what his team learned as they experimented moving away from a sidecar-heavy setup—and how Watt can help simplifying operations and boost performance.

We’ll dig into:

✅ Why sidecars often become bottlenecks at scale

✅ The hidden tax on observability, networking, and deploy times

✅ How Spendesk re-imagined their stack using Watt

✅ What changes when infrastructure becomes app-native

If you're deep in the weeds of service mesh, observability agents, or just tired of debugging YAML for yet another sidecar—you’ll want to hear this one