3 ms·
Going into a public Cloud has massive advantages. The problem is, most people simply use it wrong... - They don't right-size their instances: AWS provides a se
by movedx 4y ago
Going into a public Cloud has massive advantages. The problem is, most people simply use it wrong...
- They don't right-size their instances: AWS provides a service for this
- They don't using scaling correctly - they just stick to static instances
- They don't scale VERTICALLY, as well as HORIZONTALLY, during a scaling event
- They don't agree to a minimum term or pay anything up front even though they know they will need it, they just stick to on-demand pricing
- They don't use the whole suite of services to build their architecture: it's just EC2 and ALB and off they go
- They use `AdministratorAccess` for all IAM Users and you end up like Uber
I love the idea of hosting on cheap, physical tin - look at the prices Hetzer can get you - but the goodies you get from Cloud cannot be ignored. The automation around provisioning resources alone is simply too powerful (especially when you combine it all with Terraform.)
Then there's the ability to pay for resources up front and STILL be able to "chop" up what you paid for into different units of compute. You can spend $5k/year on a big, fat server and then split it into 15 smaller servers if you like. Same price. No surprises on cost at all.
Egress traffic is the biggest cost, by far, but that can be architected around.
In the case of the article, though, it sounds like they should have gone bare metal to begin with because location is basically irrelevant to them (another example using Cloud wrong.)
- TheLoafOfBread 4y agoAdditionally from my experience with AWS - licenses for EC2 or RDS gets sorted automatically. - Easy, centralized and automatic patch management of EC2 servers. - If something is getting outdated, AWS will start sending emails so you can upgrade in some favorable time. - Simple scaling of space, I don't need to buy SSDs compatible with my server, I will just ask for more space and few minutes later I got it.
- mekster 4y agoI have a feeling people feel "cool" for knowing how to combine AWS services and pretend it's the modern magical way, in fact they're just feeding themselves to AWS by not having radical thoughts. One instance with some knowledge running your own pieces can do quite some wonders. But young kids compete by how many buzzwords they know.
- movedx 4y agoYou see, you've made quite the fool of yourself here. I actually run my own hardware on a 250mbit fibre line from my garage. I have several systems in there and know what "running you own pieces" can do for you. I'm also close to 40 years old. I'm probably older than you are. I would have gladly engaged you and offered you what I know, but you've chosen to attack rather than work with. Good luck.
- fatnoah 4y agoIn a past life, I led the migration from datacenter-hosted infra to AWS, and the net result was that we were able to actually increase the size of our infra to support full geo-redundancy, but pay ~40% less to do so. Our app usage had a massive range of requests per second from single digits during off hours to many hundreds during peak hours. By modeling our usage, we were able to combine reserved capacity with appropriate scaling to manage our costs. Since our customers were primarily on mobile, we'd already invested heavily in minimizing egress traffic. Finally, making full use of many of the management tools aved labor costs, so a smaller operations team could support the business.