Over the past few months, I’ve been working on a few Amazon Web Service (AWS) ‘things’. The way I look at it, there are a few major goals for using the public cloud.
- Cost savings
- No more hardware
They’re really all related the more I think about it. You can scale a web application in your own data center, but that’s a lot of equipment to buy, and odds are, it won’t be used all the time, only during peak hours, days, seasons, etc. If you were to build out your own infrastructure for peak season, you’d have a ton of machines off or idle. If they’re idle, you’re still paying for power and cooling.
The reason I wrote my first book on scaling a web application at AWS is to point out that getting started is simple. AWS has a million (or so it seems) features and capabilities, which is awesome, but, it can be overwhelming. Get started simple. Put a web application on a few EC2 instances (virtual machines) with an Elastic Load Balancer (ELB) in front of them. When the load spins up, let AWS spin up more servers from you (Auto Scaling Groups).
Don’t be intimidated. Give if your First Try.