Your team debates microservices, Kubernetes clusters, and serverless—because everyone’s doing it. But what if the right choice is… none of them?
The “You Ain’t Gonna Need It” (YAGNI) principle isn’t about rejecting modern tools. It’s about rejecting guesses. Here’s the truth: Most projects evolve, and so should their architecture. Start simple. Scale deliberately.
In this talk, we’ll tackle:
Simplicity’s superpower: Why monoliths (or better: Moduliths!) still win for early-stage clarity
Evolutionary design: Letting requirements—not trends—dictate your tech stack
Complexity traps: Spotting overengineering red flags (e.g., “future-proofing” that never pays off)
When to pivot: Signals that it’s finally time to embrace those microservices
Real-world examples include a startup that scaled to 1M users on a “boring” monolith and an enterprise that saved $2M/year by deleting unused Kubernetes clusters. You’ll walk away with a filter for cutting through tech hype, aligning your architecture with today’s problems—and leaving tomorrow’s for tomorrow.