[poxrud]

The strength of AWS does not come from any individual offering, but from the way the many services effortlessly tie together. Job queues, email/sms services, databases, all available under the same api. Sure I could install my own open source versions of these but I'd rather spend time writing code than worrying about security patches and updates.

For me the biggest game changer was realizing the true power of lambda, and I'm not talking about using it as an http responding webhost as most blogs describe. But as a way of reacting to events within your infrastructure. Any AWS service that can generate an event can have a lambda function associated with. Run code on file uploads, database updates, completion of backups ...the possibilities are endless.

[nameless912]

> effortlessly

Uh...have you ever actually used AWS? There's friction all over. It's certainly not a seamless experience going from API to API.

[rmdashrfstar]

Your comment is unproductive and unnecessarily sarcastic. It would seem obvious the parent has used the services provided by AWS, and your focusing entirely on the perceived negatives and friction when combining services is not constructive.

Are you suggesting there is less friction in using multiple softwares, likely as self hosted, produced by separate developers, compared to using services hosted by AWS which allow you to only worry about building your product and managing links between services? The latter almost undeniably leads to greater productivity over the former, and if you're interested more about building and delivering a software product, that must be preferable.