3 ms·
For what it's worth, I really don't like AWS - aside from their S3/Route53/CloudFront products. There is a layer of abstraction that is so minimal that you may
by beardedman 7y ago
For what it's worth, I really don't like AWS - aside from their S3/Route53/CloudFront products. There is a layer of abstraction that is so minimal that you may as well roll out the services yourself & save a ton of money. Of course, if you like that layer, then that's fine too.
- Aperocky 7y agoIf you look beyond that, AWS offer layers of services that you might not realize existed. Cloud DB with no worry about physical hardware (in addition to S3 buckets which is mostly for files). lambdas when you don't want to manage a server, cloudformation when you don't want to manually start your stack by clicking, API gateway for quick ways to create APIs without worrying about stuff. And powerful orchestration layer that connects all of these together. In fact, a lot of these services are bootstrapped on AWS itself. If you know your way around AWS, you can really find a sweet spot where it's cheap scalable and mostly worry free. The problem is that AWS domain knowledge in itself is _deep_ and not many people know enough about AWS to avoid large amount of pitfall and inefficiencies that a knowledgeable people can quickly spot and fix/alternate.