Comment by donavanm

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.