6 ms·
It actually can make more sense for larger websites than for smaller ones, as Pinterest can scale with demand and thus be running 50% or less VMs during quiet p
by Someone1234 11y ago
It actually can make more sense for larger websites than for smaller ones, as Pinterest can scale with demand and thus be running 50% or less VMs during quiet periods (e.g. middle of the night).
I'm not exactly sure how you jumped from them using AWS to the assumption that they're "throwing more hardware at [their] problems" rather than optimizing their software. AWS or other cloud services don't really indicate a certain priority as far as internal development, just like first party hardware doesn't (and there are companies that throw additional hardware at problems, just like there are companies that throw extra virtual capacity at it).
- toomuchtodo 11y agoAWS margin is so much higher than your own physical hardware, therefore its cheaper to throw your own hardware at the problem instead of AWS resources (and their built int margin), before finally contemplating spending expensive engineer time on it.
- merb 11y agoit's not. Most people forgetting maintenance costs. They are raising much higher in non Cloud environments. Instead of tracking just your load and buying servers you need to track EVERYTHING. Hardware failure, replace it, etc. Also networking, it's really really really hard to run a Big network. AWS VPC is easy, AWS VPC is predictable. A normal network is not predictable. People forget about a lot of things, especially that it isn't that easy to buy hardware and put it into a datacenter. Also renting the datacenter or buying it? What about the clima? Do you need special coolers etc? What about raising electricity cost? Or higher network costs to your t2, t1 provider? On AWS a box costs x Cent per Hour and most likely these prices will fall. You only need to pay that. We run on AWS and especially due to the networking we pay less than we would pay in a normal datacenter. Mostly cause of the fact that they want money for everything. Even in the small scale, just buying 3-4 AWS instances upfront is really really cheap.
- toomuchtodo 11y agoI do Devops/Infrastructure for a living, I've shown the math to both my day gig and numerous consulting clients that AWS is 30-40% more expensive, even when taking into account reserved instance pricing. External networking expecially is super expensive compared to traditional transit pricing. They're absolutely wonderful for bursty or async workloads, but if you know your load, you're better off on your own gear. EDIT: Source added. https://blog.serverdensity.com/saving-500k-per-month-buying-your-own-hardware-cloud-vs-colocation/ https://blog.serverdensity.com/saving-500k-per-month-buying-... "Saving $500k per month buying your own hardware – cloud vs colocation" The article mentions SoftLayer, but its just as relevant for AWS.
- merb 11y agoI didn't meant external networking. Connect two datacenters, see what costs come up. Connect machines inside your datacenter, etc.. Your maintenance cost will raise. AWS is cheap. Whatever you did, you operated on a really slow scale where money didn't mattered. Or you completely forgot a lot in your calculation. Oh and here is a Link from Zynga: http://readwrite.com/2015/05/12/zynga-data-center-amazon-aws-public-cloud http://readwrite.com/2015/05/12/zynga-data-center-amazon-aws... My next examples would be Gilt, etc. You can't run elastic in your own datacenter. From your article: > https://blog.serverdensity.com/saving-500k-per-month-buying-your-own-hardware-cloud-vs-colocation/ https://blog.serverdensity.com/saving-500k-per-month-buying-... > Dell R415 with x2 processors each with 8 cores, 32GB RAM, a 500GB SATA system drive and a 400GB SSD This one made me laugh...
- toomuchtodo 11y ago> AWS is cheap. Whatever you did, you operated on a really slow scale where money didn't mattered. Or you completely forgot a lot in your calculation. I've managed thousands of instances in AWS, and I've managed thousands of servers in colos, both owned (DOE facility, web hosting startup, consulting firm) or with the space leased (Equinix, Savvis, Cogent, IBM). You could most definitely run elastic workloads in your own datacenter now using Docker containers, and one of the many orchestration frameworks that exist for it. As I mentioned above, if you don't have a predictable workload, AWS is great. Exceptional even. But if you know your workload and can hire 2-3 people to manage it (which you should be doing at scale), its cheaper to get your own gear and colo it.
- Retric 11y agoAWS margin is only relevant if you can be as Efficent as Amazon if you don't have 24/7 need for 100% of your servers then Amazon is likely to be more Efficent internally. It's also highly negotiable at scale. Do 10k per month and you get standard rates, do 200k and you get a little leverage. Do 2M per month and it can be a level playing field.
- toomuchtodo 11y agoCost savings start (moving to your own hardware) at $50K/month spend with AWS. I'd imagine the cost savings are enormous at $2MM/month, although I'll need to dig my spreadsheet out to know for sure.
- deleted 11y ago[deleted]
- Retric 11y agoI doubt you can get accurate numbers for 2MM/month accounts without actually having a 2MM/month account to shop around with. Though if you have real numbers I would love to see them.
- fweespeech 11y ago> It actually can make more sense for larger websites than for smaller ones, as Pinterest can scale with demand and thus be running 50% or less VMs during quiet periods (e.g. middle of the night). You do understand we can buy things at 33% the price AWS charges, right? And have 24/7 access? Oh, did you know you can do the same thing at other providers for cheaper? :| AWS is overpriced.
- eli 11y agoIs it not possible that the peak load is more than 3x the average load? With your own hardware you have to be provisioned for peak load 100% of the time.
- fweespeech 11y ago> Oh, did you know you can do the same thing at other providers for cheaper? :| https://www.stormondemand.com/servers/baremetal.html https://www.stormondemand.com/servers/baremetal.html 32/64GB - $0.75/hr https://www.linode.com/pricing https://www.linode.com/pricing 20/64GB - $.96/hr and bandwidth http://aws.amazon.com/ec2/pricing/ http://aws.amazon.com/ec2/pricing/ 16/64GB - $1/hr + bandwidth costs @ [varies] Even if you take your premise at face value, AWS is literally the most expensive option. Personally, I've never seen a real world use case where you dropped below 33% capacity. In practice, you can get hourly billing for cheaper than AWS anyway with providers large enough to meet most customers needs.
- tracker1 11y agoLinode, and most alternatives, don't have S3/Blob storage as a service.. also missing are distributed key-value storage as a service and sql as a service. Generally, with any given service as you can scale it makes sense to run your own instances.. but realistically someone who knows insert-tech better than AWS/Azure admins is a pretty rare breed, and having to in-source those specific skills costs in terms of time and money, redundancy even more so. If you have a team of 3-5 people, you can do far more with AWS or Azure than you can most alternatives... Employees aren't free.
- 11y ago