A few months ago, I was brought in to audit the infrastructure of a post-Series A fintech company that was bleeding cash. The leadership team couldn't understand why their monthly Amazon Web Services bill was hovering around $14,200 while their actual traffic—measured at the edge—peaked at roughly 35 requests per second during business hours.
Thirty-five. That is not a typo. That’s about 2,100 requests a minute. A single Raspberry Pi 4 running a bare-bones Go HTTP server could handle that workload while sitting on a kitchen table without breaking into a sweat.
Yet, when I opened their AWS console, I was greeted by the standard modern cathedral of resume-driven engineering: fourteen microservices running across two dozen EKS pods, an Aurora PostgreSQL multi-AZ cluster with auto-scaling read replicas they never touched, three NAT Gateways passively draining cash just to let private subnets talk to the internet, managed MSK (Kafka) for event streaming between services that sat two feet from each other, and a Datadog integration burning an additional $3,800 a month ingest-logging every single health-check ping.
The founders genuinely believed this was what "modern, resilient architecture" looked like. They had read the blog posts from Netflix and Uber. They had hired well-intentioned mid-level developers who had only ever worked inside AWS dashboards and honestly believed that unless you wrap an API in three layers of orchestrators and a service mesh, your system will spontaneously combust.
