Comment by YetAnotherNick

I see what you are saying but we are speaking of slightly different things. Let’s say you need a piece of software that effectively is full text search but you don’t know that such a thing exists. Since you don’t know what you don’t know you are at a disadvantage when looking for a solution. But knowing that something like Elastic Search or Postgres’ full text search is a thing will mean that I can have a starting point to look at what is possible.

Imagine for a moment that you didn’t know that S3 was a thing. You would end up rolling some sort of home grown solution that would be less robust and possibly more expensive. You don’t need to use it, but knowing that it exists and being able to reason about its basic promise is a good thing.

AWS has grown so huge that they have everything from hosted Valkey to satellite launchers. And knowing that launching satellites is an option is valuable, but unless you know to look for it you won’t find it. And the larger the number of offerings the more difficult it is to keep up with what is possible.

To bring it back to the concept of an enterprise team to manage stuff, doing something like managing 10,000 EC2 instances manually is less good than using something like Cloud Formation. But is Cloud Formation better than some other orchestration system? You can hopefully see where this is going.

> ”You start with a problem and find solutions, not navigate solutions to make problems for.”

Ideally. But that’s often not how corporate IT works.