ECS vs EKS: The Decision I Regret (And What I’d Do Differently Now)
The author reflects on their decision to choose Amazon EKS over ECS for a new service, acknowledging that the complexity of managing Kubernetes outweighed its benefits for their use case. They describe how operational challenges with logging, deployments, and scaling emerged over time, leading to production issues during traffic spikes. The author concludes they would now choose ECS with Fargate for its simplicity and reduced operational overhead, especially for workloads that don't require deep Kubernetes customization.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3856978) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Harsh Thakkar Posted on May 1 ECS vs EKS: The Decision I Regret (And What I’d Do Differently Now) #aws #productivity The first time things broke in production, I didn’t even know where to look. Not “figuratively lost.” I mean literally. Pods were restarting. Logs were half there. Metrics were… somewhere. And I was SSH’ing into nodes like it was 2016, trying to understand why a simple Node.js service decided to disappear mid traffic.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
