yunwal
2 hours ago
Starting a new service was a path towards promotion at AWS, so they ended up launching 100s of services to the point where there were 10 different ways to do everything. I’m glad they’re culling them.
donavanm
35 minutes ago
There were (are?) challenges in product placement and compatibility as well. Yes, some “services” are very niche and dont have a credible target market/adoption plan. My old service is one of those on this list.
But there are others where a “service” is really a _feature_ of another existing product offering. But for handwave reasons it can be extremely difficult to implement that way, and a new API and service name etc make the development tractable. To throw a stone Cloudwatch org is an interesting example of this, where its both too broad and too narrow, leading to an umbrella of undersized feature/services.
sunrunner
2 hours ago
I guess this explains why AWS manages to run the whole gamut from the most generally applicable tooling such as EC2 to something I’ve never heard of and sounds specific enough to just be its own business, ‘AWS HealthOmics - Variant and Annotation Store’