> I think the diagram is for to enterprises which adore the complexity Bingo. Anecdotal experience: I saw this happen at my last position where they did an ove

> I think the diagram is for to enterprises which adore the complexity Bingo. Anecdotal experience: I saw this happen at my last position where they did an over-complicated/fragile WordPress setup with K8s. We went over to K8s for "performance optimization", "security", and "system stability"... what bothers me the most as a WordPress expert (specifically with HUGE/redundant rollouts) is that none of these reasons/bottlenecks were studied before designing the infrastructure. K8s is great, but if we start throwing arbitrary infra at our problems all we see is increased complexity without addressing the core tech issues. When I pushed to load test the new infra it was met with crickets - likely because that was never the goal in the first place. The goal was to jam a sexy technology into our stack so someone's quarterly goals were met with some lookin' pretty/SF-deluded engineering director that touts not knowing development/architecture makes him better in his role. Honestly - it's just job security, chasing a dragon, and cargo-cult for most of these orgs... if we were actually on the hook for "more with less" you would NEVER see an atrocity like what was posted. KISS is sure out of style when it comes to these fool's outrageous egos/budgets.