These anecdotes are great, but, and I'm being honest here, I don't care about 450% growth or how many millions of container instances that are reportedly runnin

These anecdotes are great, but, and I'm being honest here, I don't care about 450% growth or how many millions of container instances that are reportedly running. I care about long-standing bugs being fixed in a timely manner. Take a look at any random Github project that's unmaintained. That's the image Amazon has been showing the development community when they look at ECS. They don't see the closed source work. They don't see the hundreds of millions of internal KPIs ticked per week. Now, I haven't spoken with a developer advocate, but I'm happy to share some of my frustration with you: I've had a dedicated resource working around bugs and limitations in ECS for months. We built a service mesh because ECS lacks service discovery, and then we built wonky patches to work around weird bugs in ecs-agent regarding how containers identify themselves. We've spent serious, deep time tracking down intermittent failures in the scheduler. We've worked in and around the strange task abstraction. This hasn't been a lovely experience. It's been hard and painful, but we press onward only due to the lack of time to convert to Kubernetes/Istio. Are you in Seattle? Shoot me an email; I'd be happy to grab a coffee and share our experience.