I get the point, that with sufficient branding to a target audience, the issue is negated, but I think you're conflating branding for a corporation with branding for niche products. The level of effort put into branding the corporation at large versus the level of branding for any individual service is orders of magnitude apart.
Importantly, with AWS, there's dozens of services, all competing for a three letter address space. It's getting saturated, so it's easier and easier to get confused.
> Sure, not everyone will need EKS and it becomes more esoteric, but people that do it day-to-day know exactly what EKS is.
This is sort of my point. I work with kubernetes and kafka. The kafka instance that I connect to is managed, the k8s cluster I deploy to is not. I can't tell you off the top of my head if EKS is managed k8s or managed kafka. That was the breaking point for me to stop putting effort into trying to remember.
I have pretty severe ADHD, so I can accept that I'm probably outside a standard deviation as far as ability to remember three letter acronyms, but I think I still stand as a contradiction to your assertion.
Importantly, with AWS, there's dozens of services, all competing for a three letter address space. It's getting saturated, so it's easier and easier to get confused.
> Sure, not everyone will need EKS and it becomes more esoteric, but people that do it day-to-day know exactly what EKS is.
This is sort of my point. I work with kubernetes and kafka. The kafka instance that I connect to is managed, the k8s cluster I deploy to is not. I can't tell you off the top of my head if EKS is managed k8s or managed kafka. That was the breaking point for me to stop putting effort into trying to remember.
I have pretty severe ADHD, so I can accept that I'm probably outside a standard deviation as far as ability to remember three letter acronyms, but I think I still stand as a contradiction to your assertion.