17 ms·
He kind of touches on this in point IV, but never mentioned specifically: the cost comparison is not AWS vs ovh. It's fragment-of-EC2 vs ovh. If you need a pre
by viraptor 6y ago
He kind of touches on this in point IV, but never mentioned specifically: the cost comparison is not AWS vs ovh. It's fragment-of-EC2 vs ovh.
If you need a predefined small number of VMs and no other functionality, it would be silly to go with AWS. But on the other hand, if you want a set of servers of a given class spawning on demand, with traffic coming in via load balancers, with integrated certificate and DNS management, with programmable lifecycle hooks, with integrated authn/authz, with full audit logs and account management, with configurable private networking to other services, etc. etc. ... You'll pay more than the price difference for someone to implement all of that from scratch.
Compared to this many other points sound like conspiracy theories. Meanwhile people either don't know they can do better, or use AWS because they want more features.
- KingOfCoders 6y agoMany people use AWS because everyone uses AWS. Many of my clients have no need for AWS but still use it, at least until the VC money runs out. Usually then I have to go first, then servers are moving to somewhere cheaper when a new CFO comes in.
- lvh 6y agoIt's possible that "many" firms do this, but given AWS' growth numbers that would imply they don't really spend meaningful amounts to begin with. Counterpoint: I've seen a great many false economies with people trying to go on-prem and do alternative hosting because they don't think the AWS premium for e.g. GPU instances is worth it. I don't think that has generally worked out well.
- KingOfCoders 6y ago"It's possible that "many" firms do this, but given AWS' growth numbers that would imply they don't really spend meaningful amounts to begin with." I could spend a million EUR a year on AWS without the need for most of the services of AWS? But it YMMV and 1M EUR/y is not meaningful, perhaps we differ there.
- qaq 6y agoThere is no good data to prove either statement. You could def prove that for some large scale onprem for a given type of problem is cheeper than the cloud.
- freeone3000 6y agoThe AWS premium for GPU instances is absolutely not worth it. You don't hear about people running local GPU compute clusters because it's not newsworthy -- it's obvious. Put a few workstations behind a switch, fire up torch.distributed, you're done. And after two months, you've beaten the AWS spend for the same amount of GPU compute, even if only 50% of the time is spent training. Timesharing is done with shell accounts and asking nicely. You do not need the huge technical complexity of the cloud: it gets in the way, as well as costing more!
- srtjstjsj 6y agoWhat if you want 10x the GPU for one month to build a model?
- freeone3000 6y agoThat's the only scenario I can think where it comes out clearly in favor of AWS - you've tested your model in the small on Colab, you're confident you'll need only a few training runs, you can schedule them in us-east, and you can inference on CPU, and you won't need to rebuild for another eight months (when purchased cards become outdated). It's not an impossible scenario... But imagine the sort of company that trains their own model instead of using a huggingface refinement or an off-the-shelf redistillation. (These can be done reasonably on an average gaming PC, no need for a cluster.) Such a company has expensive human resources. They bothered to get a data scientist and at least a research engineer, if not a full researcher. Were they hired on six-month contract as well? This is a huge expense, so it must be an important differentiator to have built a custom model -- and it's a one-and-done? I don't see it. I think it's going to be an ongoing project, or it shouldn't have been approved in the first place.
- Cthulhu_ 6y agoFrom AWS' own marketing propaganda: How much would said clients have to invest in people and hardware otherwise? What if their application becomes an overnight success and needs to scale up fast? Sure, if it's an established company then using their own hardware (and people to set up and manage it) might make sense; iirc Dropbox is a fairly recent big player that made that move. But otherwise it's a big upfront investment to make, and you can't know if it'll pay itself back. So sure, AWS can be 2x or more as expensive as renting servers at a company like OVH or building your own datacenter, but it's paid by the minute if need be, not all in one go. If your startup or its VC money runs out in six months at least you can quickly scale down and pull out.
- bsenftner 6y agoFor my own startup, I built a small cluster of 17 servers for just beneath $55K, and that had a month-to-month expense of $600 placed in a co-lo. In comparison, the same setup at AWS would be $96K per month. And it is not hard, easy in many ways. Do not be fooled, the cloud companies are peddling is an expensive scam.
- Retric 6y agoCloud companies are useful as long as you want what their selling. The best case is needing say 2 TB of ram for some workload or test that only going to take a few hours. Or something like the Olympics where 95% of your demand comes in a predictable spike across a few days.
- chasd00 6y agovery true, the original selling point for Cloud was instant upgrade/downgrade as needed. That was the original amazing thing, dials that said RAM and CPU you could turn up or turn down.
- ti_ranger 6y ago> For my own startup, I built a small cluster of 17 servers for just beneath $55K, and that had a month-to-month expense of $600 placed in a co-lo. In comparison, the same setup at AWS would be $96K per month. Why would you build exactly the same setup in AWS as for on-prem, unless your objective is to (dishonestly) show that on-prem is cheaper? Lift-and-shift-to-the-cloud is known to be more expensive, because you aren't taking advantage of the features available to you which would allow you to reduce your costs.
- WrtCdEvrydy 6y agoAWS also gives you a lot of cost savings for using Spot and signing contracts with minimum spends. Only a small shop pays full price for anything.
- shiftpgdn 6y agoOkay but then you have to engineer your application around interuptable spot instances. You're also making a 36 month commitment when you sign that contract (generally buying the hardware for Amazon.)
- WrtCdEvrydy 6y ago> you have to engineer your application around interuptable spot instances This is where your ALBs and ASGs come in. If your app doesn't use local writing and you can shift your caching to a shared cache, the cost savings are good.
- ehnto 6y agoI work in an ecommerce agency environment and it can be quite frustrating. Every client, no matter how small, has been sold the spiel and had some guy come through and build a boutique cloud infrastructure, CI pipeline and development VM. As if traffic will increase 1000% by next week with no prior warning. It just doesn't happen like that. I spend half my time debugging Hyperscale Bullshit™ that the client never needed and that failed the moment the devops guy left. If you want this stuff, you need a long term tech team, and a devops member on hand. Every time you hand your project around this stuff costs you hours. You also need to tell your devs to use the devops guy like tech support. They built this rickety tower of obtuse config files, make the devops guy fix it and don't let your devs spin their wheels for 4 hours before their assets compile on the Super Cool Distributed Docker VM microservice stack of teetering jenga blocks.
- michaelbuckbee 6y agoI did work for a YC startup that replaced my ~$100/mo Heroku app with a $5,000/mo AWS stack that nobody in the place knew how to manage. Their site was so ridiculously low traffic that I did some napkin math and figured out they were paying around $0.10 per web request.
- jrochkind1 6y agoHuh, making a manual AWS stack 50 times more expensive than a heroku setup seems like a real trick to me! I'm used to heroku being more expensive than running it yourself -- as I would expect, since you're paying them for a lot of management.
- user5994461 6y agoHeroku is both incredibly cheap and incredibly expensive. It's only $7/month to deploy a web application. More if you want some of the paid features and a database instance. It all works out of the box with instant deployment out of the box, it's fantastic. Then it suddenly goes $50 more per gigabyte of RAM, which makes it massively expensive for any serious workload. It's crazy hot much they can try to charge, makes AWS looks like a bunch of clowns in comparison.
- Spivak 6y agoAt my company we colo at a few local datacenters and have do deal with a huge amount of pressure from our investors as to why we're not using AWS. The points that always seem to come up: * AWS is a known quantity and it's easier to evaluate our business with it. * AWS provides "outage damage control" because AWS outages make the news and customers are more understanding. When our ISP has issues it just looks bad on us. * Our company doesn't look as innovative because we're not cloud. Bleh. Our app is compute, storage, and data transfer heavy but switching to AWS being a, literally, 10x cost for us is apparently not enough a good enough answer.
- mwcampbell 6y agoHow do you do failover if a server fails or if connectivity to one of those datacenters is lost? With AWS I could just set up a multi-availability-zone RDS deployment for the database and an auto-scaling group for the web tier and be confident that AWS will recover the system from most failures. To me, that is the major selling point of any of the hyperscale cloud providers.
- KingOfCoders 6y ago"connectivity to one of those datacenters is lost" Anecdotal, but AWS had more global problems than the triple connected data centers I've used in twenty years. I suffered through many rough times, data center connection or power problems were not (very seldom) one of those. Most of the problems came from apps that we didn't build well to scale or that had bugs (most frequent cause of problems and sitedowns).
- HelloNurse 6y ago> With AWS I could just set up a multi-availability-zone RDS deployment for the database and an auto-scaling group for the web tier and be confident that AWS will recover the system from most failures "Confident"? "Most" failures? Are you merely hopeful that the probability of a bad failure is low, or are you able to test the AWS resiliency techniques you mention and to ensure that they stay working? At what cost?
- darkwater 6y agoAbsolutely. But they also charge you independently for (almost) all those services. So, you are somehow still paying for a sort of "comfy lock-in" (no native speaker here so try to follow me even if words are not the exact ones) because you cannot access those services from another pure CPU resource on another (cheaper) provider. Basically, AWS is squeezing as many dollars as possible from your pockets (good for them).
- drchopchop 6y agoAWS gives you all the things you'd need to scale, without heavy up-front costs. There's a natural path from small instances -> bigger instances -> load balancers/ELB -> reserved instances (or spot if it fits your workload). For a smaller company, any savings you'd get from owned servers would be offset by much higher dev ops costs. Plus, as mentioned, you get a vast menu of services to choose from, all of which are managed. Just in terms of databases alone, you could go with RDS (raw MySql/PG), Aurora, Dynamo, Elasticache/Redis, DocumentDB (Mongo) and more. Plus managed backups, failover, multi-AZ, security, and connectivity built-in. If your team is filled with devops engineers, then, sure, go with the non-AWS route. But it's a lifesaver for agile companies who can't afford a lot of infrastructure work and need easy levers to scale, and can afford a modest markup.
- tw04 6y ago>can afford a modest markup. I'm with you until that statement. AWS is nothing approaching "modest" in their markup. 20% minimum and typically much higher if you know how to negotiate when purchasing your on-prem gear. And if you happen to be a shop that sweats assets for 7+ years that number starts being measured in the hundreds of percentage points more expensive.
- whatshisface 6y ago>And if you happen to be a shop that sweats assets for 7+ years that number starts being measured in the hundreds of percentage points more expensive. If you include the growth in electric efficiency over time, it can be bad to run old servers after a certain point.
- nixgeek 6y agoBut again, is that comparable? Seems like apples versus oranges. What’s the connectivity into your 7+ year old asset cost? What about the space, power and cooling to provide it a home? What happens when your environment gets attacked by a volumetric DDOS, is that 100Mbps circuit going to get overwhelmed? I’m not arguing AWS is cheaper, simply that there are lots of things around the physical server which also have costs and complexities.
- PragmaticPulp 6y ago> You'll pay more than the price difference for someone to implement all of that from scratch. This is a common trap for startups. AWS has been around long enough that everyone has a 1st-hand or 2nd-hand horror story about someone with a $5000/month AWS bill for a basic website. This creates a false narrative that AWS is bad and or dangerously expensive. Or worse, that clever devops engineers can simply roll their own solutions with open source tools for half the cost. The reality is that if a startup truly needs $5K/month of AWS services, they’re getting a bargain by buying it from Amazon instead of building it out themselves. $5K/month won’t even begin to buy you another qualified devops engineer to build and maintain custom infrastructure. The first rule of startup engineering is to use every tool available at your disposal to get to market as fast as possible. Cost reduction can come later, but you can never get back wasted time spent rolling your own solutions when an off the shelf vendor could have solved your problem in days rather than months. However, the other trap is when inexperienced or overeager engineers see the long list of AWS product offerings and think the goal is to use as many of them as possible. There are some misaligned incentives for engineers who want to gain as much AWS experience as possible on their employer’s dime, regardless of whether or not it’s the right business decision. Worst case, mid-level engineers use as many AWS services as possible so they can pad their resumes, then use the experience to pivot into a higher paying job elsewhere and leave the startup with a mess of half-implemented, unnecessary AWS infrastructure and no one to maintain it. Unfortunately, it happens frequently in the startup world where companies are more likely to hire junior engineers who are eager to tinker with AWS and build their resumes. The brute force way to avoid this problem is to simply constrain the engineering team to a less powerful platform like OVH or DO. If you don’t need any features of the bigger clouds, this works. However, as soon as you do need the big-cloud features you’re going to waste huge amounts of money building them out yourself. It won’t show up on the monthly provider bills, but rather be hidden in the much higher engineering costs and longer project timelines. The real solution is to hire experienced engineering leadership who will keep complexity in check, then use AWS or other big cloud providers responsibly.
- kikimora 6y agoCan you share a story about how AWS helped to remove or redeuce spend on devops? In my experience with AWS you would get $5000/month for a basic website and also would be paying devops to manage AWS.
- an_opabinia 6y agoSounds like you're listing the enterprise features people pay for. If Amazon sells it so cheaply why don't enterprises go direct to Amazon instead of paying a SaaS provider like you? It's about economics not accounting. Once you get into cost comparisons you've already lost. AWS is purpose built for an accounting narrative. To illustrate what a dead end accounting is, accounting can't explain things like, "I spend money today to possibly make money more than 1 year in the future." That's basically every startup and accounting doesn't have a story for it. Of course a free tier looks good accounting-wise. How does one "account" for lock-in though? If you can't figure that out you will not convince bean counters to consider alternatives. And good luck teaching economics (as opposed to accounting) to bean counters. Here are a few compelling explanations: the cheapest bid (i.e. free tier) is always the worst one. Some people are so addicted to accounting storytelling - as a way to organize their world, a whole philosophy - they are actually always convinced the cheapest bid is always the best one. Another: AWS is so overpriced, the $50k you spend on developing against AWS services to use $500k of "free credits" will deliver less value than $50k you spend developing for a single vertically scaled beige box computer with simple ergonomics and running it.
- romanoderoma 6y agoDon't know why you are being downvoted, but I agree with your reasoning. I've worked most of my career in places where technology was king and AWS is certainly technologically ahead of its competitors. Fast forward a couple decades and I ended up in financial institutions where economics is king and they don't use AWS, not as much as they should, if you listen to the average internet guru. Not because AWS doesn't do what they say it does, but because economically it's not advantageous, at least until it is. Which is not at the beginning. To put it in simple words: they don't ask "are we ready to scale" but instead "are we making money out of this".
- 908B64B197 6y agoExactly. That and the 9's. I don't know how good OVH is with outage and availability. Sure the raw compute is cheaper. There's also storage. He's renting physical drives on OVH meaning he has to take care of replication and back-up himself. The disks in his AWS VMs should be persistent. If his OVH server goes down due to hardware failure, what happens to his disks? I genuinely don't know. Lastly, OVH doesn't have regions everywhere. Then it's yet another different provider with slightly different product for every geographical region he wants to support.
- ianhowson 6y agoAllow me to educate you :-) > I don't know how good OVH is with outage and availability. I've personally observed failure rates similar to AWS EC2 and EBS. You need to plan for failure, like any cloud provider. > the raw compute is cheaper Dramatically so. 20% of the price. > There's also storage You can get local NVMe, cheaply, with literally 100x the perf you can get with the most expensive EBS volumes. AWS does not have a storage offering that comes close, not even their instance store NVMe. > what happens to his disks VM images can be backed up automatically without downtime (on a schedule, not live.) They offer an EBS equivalent. > OVH doesn't have regions everywhere They have enough. us-west, us-east, eu-west, APAC, others. I'll grant that the US regions are operated by a different corporate entity and a different web interface, and that is annoying.
- 908B64B197 6y ago> VM images can be backed up automatically without downtime (on a schedule, not live.) They offer an EBS equivalent. But if you need to persist transactions you still need to replicate and persist state yourself. Or can I mount an OVH virtual drive that I know will survive across VM migrations? > I'll grant that the US regions are operated by a different corporate entity and a different web interface, and that is annoying. Why? Do they at least support the same API? Can OVH actually scale on demand?
- ianhowson 6y ago> Or can I mount an OVH virtual drive that I know will survive across VM migrations? Yes, Block Storage: https://us.ovhcloud.com/public-cloud/block-storage/ https://us.ovhcloud.com/public-cloud/block-storage/ > Do they at least support the same API? Yes > Can OVH actually scale on demand? Not as big as AWS, but yes. Remember that you're getting 5x the compute resources for the same money. You don't need to autoscale as much. You're not fighting crappy EBS performance. You're not architecting around remote-network RDS databases with milliseconds of RTT. I firmly believe that for most applications you're going to be better off just massively overprovisioning your hardware and keeping the software stack simple.
- npsimons 6y ago> You'll pay more than the price difference for someone to implement all of that from scratch. I also think the "pay someone to set this up" factor is underestimated. Person time cost eclipsed computer time cost a long time ago. If you've got the market demand to need that kind of infrastructure, you're almost certainly operating at a scale where you can afford to dish out the extra dough because it will reduce downtime and overhead enough to make the ROI worth it. I'm not an expert in this (I'm just a code monkey who works with scientists, and side hustles as a small time sysadmin), but reading books like "Release It!" and reading blogs (especially DevOps, as I'm looking at getting into that) gives me the impression that if someone could reduce their costs while still getting the value AWS gives, they'd be doing it. I mean, maybe it's a well-kept secret (especially if it gives a market advantage), but if it's so easy, I'd think everyone would be doing it, and AWS would be out of business. Edit: I concede that startups probably don't need AWS; what I'm thinking of above is big, old, established companies that believe "no one was ever fired for buying AWS." But I do believe that you have to have smart, motivated people in order to grow while staying lean, and just because we hear the survivor stories of startups that do, doesn't mean there aren't dozens that die because inexperienced devs though they could do better than AWS, and were proven wrong.
- foxtr0t 6y agoThis article may be poorly written, but if you actually read through the whole thing, it makes some brilliant points: 1. IaaS providers are incentivized to create services that lure you with managed solutions that seem like a great deal on paper, while they are actually more expensive to operate than their self-rolled alternative. 2. "DevOps" and "Infra" people charged with making these decisions often follow the industry zeitgeist, which for the moment is whatever AWS, GCP, and Azure are offering. This is in spite of the best interests of the company they work for. The right decision in so many cases is what choice one can defend when something goes wrong, or what you can parlay into the next gig. If costs, performance, and features aren't closely managed, scrutinized, compared, going with a solution like Aurora/Redshift/Dynamo won't be challenged. 3. Nothing is easily comparable because these services aren't just a CPU as you mention, instead they're hardware and software rolled into one. This is intentional, and has little to do with making things easier for you. At best, IaaS providers defend this as "differentiation" but it's closer to obfuscation of true cost. Go ahead and ask your AWS rep if use case x, y, and z will perform well on lambdas and you'll likely get a near canned response that they all fit perfectly, even if y is a job with high load spread uniformly through time. The only way you can make this comparison is by creating the two services, standing them up in production for a week and checking the bill. In other cases such as FPGAs and databases, you'll have a much harder time as not only is the software/hardware offering unique, but the user code will be completely different and require entire rewrites to get what _might_ be a fair comparison.
- Aeolun 6y agoAnecdotally, my company spends several millions a year on AWS, and they do it mostly so they don’t have to think too much about the hardware every team uses to implement their solutions. I’d say the strategy is an unmitigated success, even if it costs them 3 times more than a similar on-premise (or dedicated) solution would cost. My last company went the dedicated route, and they were perpetually in need of more servers because nobody was willing to pre-plan capacity. To the point that the database team just couldn’t provision any new databases for a year.
- foxtr0t 6y ago
- hinkley 6y agoI have a small app I run just fine in Digital Ocean, but at work we care about not just geographical redundancy but geographical load balancing. Having user traffic cross the country puts you at a deficit for response times, and if that matters to your company, having servers close to clusters of users is a good thing. I can do that a little bit with DO. What are my options with OVH? I see them bragging about having the biggest data center, as if I am supposed to think that's a good idea instead of a terrible one.
- asymptotically3 6y ago>I can do that a little bit with DO. What are my options with OVH? OVH have datacentres in multiple countries just like DO.
- hinkley 6y agoThere are parts of the US that are still pretty far from the nearest DO data center. If I go AWS I don't have that problem. I should clarify that I am playing devil's advocate here. I've never been pro-Amazon (although I slipped for a bit there, I'm feeling much better again), they just have answers for some questions that I don't. Or at least, not until multi-cloud is on everyone's radar. The combined coverage map of any two AWS competitors generally looks more competitive, but we collectively have to 'work' on the people who think that would be too hard.