3 ms·
This use case is about where AWS cost effective scalability ends, anything more complicated and you are into multiple thousands a month for a redundant solution
by Railsify 6y ago
This use case is about where AWS cost effective scalability ends, anything more complicated and you are into multiple thousands a month for a redundant solution for a critical web-app with a database. We used to run prod and stage envs in aws but as our stage environment grew we realized we could on-prem some pretty bad-a* hardware for the cost of a few months AWS billing. Now we run prod on aws, staging and dev locally.
- murukesh_s 6y agoSecond that.. and hardest thing is you don't really know where you are getting charged. i mean you can look at the billing but boy they do add up to 1000s before you know and you are so hooked into auto scaling, s3, rds with multi-az what not..
- monsieurbanana 6y agoThere's a cost maintaining a staging environment on-prem while prod is on a cloud. Slightly different versions of databases, different networking, etc... It could create issues. This does depend on how much you buy into the AWS ecosystem, if it's strictly EC2-only it's not as much of a problem. Not that I wouldn't do it, a lot of times it does make financial sense.
- busterarm 6y agoYou don't exactly need to tell me. I have 10^4 machines in multiple clouds right now plus more n datacenters. Cost effective scaling is hard, but you have to design your applications around it. Tbh, I find most engineering orgs don't have the competency to pull it off.