4 ms·
> but is using one of the major cloud services cheaper than running your own? At list prices? Pretty much never. Nobody sane with installations like Evernote
by vidarh 10y ago
> but is using one of the major cloud services cheaper than running your own?
At list prices? Pretty much never. Nobody sane with installations like Evernote are paying remotely close to the published prices, though.
The cloud providers rarely make sense in terms of cost for smaller businesses unless you heavily rely on batch jobs (spinning servers up/down) or other of their more advanced services. There are many valid reasons for smaller companies to consider cloud deployments, but I've yet to see one where it was the cheaper alternative.
- koolba 10y ago> The cloud providers rarely make sense in terms of cost for smaller businesses unless you heavily rely on batch jobs (spinning servers up/down) or other of their more advanced services. There are many valid reasons for smaller companies to consider cloud deployments, but I've yet to see one where it was the cheaper alternative. The cost of a server isn't just the hourly/monthly fee for running it. It's also the cost of waking up at 3am to turn it back on. If you're managing your own bare metal then you have to deal with that one yourself and I can assure you it's never cheaper than the cloud unless you value your time at $0. Sure you can save some money by running a server yourself but if your business it as the point where that's the deciding factor in being solvent than you might as well close shop.
- chatmasta 10y agoThis is why you should run your entire application on bare metal (colo or dedicated) with failover to the cloud. The benefit of the cloud is its elasticity. You can handle a 2000% traffic increase by spinning up VMs instantly; no need to wait a day or week or month for bare metal provisioning. And you should do this! But once you've structured your application this way, you are already horizontally scalable. There is no reason the core of your capacity cannot be on bare metal, especially now that container orchestration platforms are bringing feature parity to cloud and bare metal. Only provision VMs for handling temporary traffic spikes. You can generally predict traffic costs for next 1, 2, or 3 months. You can't predict traffic spikes as easily. So why not invest in dedicated servers or collocated hardware, just enough to cover your expected traffic? Send any excess capacity, whether due to traffic spike or hardware failure, to dynamically provisioned cloud services. This way you capture the economic advantage of elastic cloud pricing while achieving full utilization of your capex investment.
- koolba 10y agoAt the dollar spend for the infrastructure for most apps, the labor costs of dealing with physical servers is not worth it. Saving $1K/month on infrastructure is meaningless if it costs me $10K in labor costs. Your numbers only work for the little guy when labor costs are discounted to zero.
- chatmasta 10y agoRenting a dedicated server requires no labor cost of your own (if a drive fails, your provider replaces it), and is almost always cheaper than the equivalent cloud resource, especially when it comes to bandwidth.
- fuzzybeard 10y agoThat still leaves sysadmins that you no longer need when using the cloud. The cloud allows your developers to run free without the need for infrastructure and sys admin teams to worry about the servers.
- 20years 10y agoVery little sysadmin needed if you go with a managed dedicated server provider. They pretty much take care of most of that for you. A little more expensive than a non-managed dedicated server but oftentimes still much cheaper than the cloud. Plus, you can't really completely get away from sysadmin when working with the cloud either. You actually get a lot less support than you do with a managed dedicated server provider. Note: I heavily use AWS and managed dedicated servers.
- vidarh 10y ago> That still leaves sysadmins that you no longer need when using the cloud Looking at our timesheets, managing cloud setups takes more time on average than managing bare metal server setups, and the amount of time spent handling hardware issues make up ~1%-2% of ops time spent on the bare metal setups for our systems. We "save" that on the cloud setups, but end up having spend more to account for dealing with crappy APIs to do all kinds of things we have much more direct control over instead.
- vidarh 10y ago> The cost of a server isn't just the hourly/monthly fee for running it. It's also the cost of waking up at 3am to turn it back on. If you're managing your own bare metal then you have to deal with that one yourself and I can assure you it's never cheaper than the cloud unless you value your time at $0. You have to deal with outages when using cloud providers too. So you design for availability in either case, and pay someone to wake up at 3am when there's an actual emergency. We're the ones taking the calls if our customers systems goes down at 3am, and it eats into my profits if it happens because they pay us monthly fees that are structured so they're far more profitable for us if nothing goes wrong. Guess what's most profitable for me? Bare metal setups. Despite the fact that we end up charging my customers less to manage them, because it's harder to justify high fees when the overall costs are so much lower. > Sure you can save some money by running a server yourself but if your business it as the point where that's the deciding factor in being solvent than you might as well close shop. I had a client last year where we cut the hosting costs including the hourly rates for operational tasks by 90% by moving them off AWS. While they were on AWS their hosting fees made up ~30% of their burn rate. It's an extreme example, but there are a lot of companies out there for whom hosting makes up a sufficient portion of their cost that it is a matter of survival for them to cut them.
- edblarney 10y ago"> but is using one of the major cloud services cheaper than running your own? At list prices? Pretty much never. " ??? It's almost always 'cheaper' for small companies to use the cloud. It costs a lot of money to pay people to figure what hardware to buy, install servers, networking gear, maintain it, pay for bandwidth, backup etc. But the cost becomes 'non starter' when you start to access all the nice things that cloud offers: Lambdas, S3, easy backups, etc. etc. and the fact that it 'scales on demand'. Then of course there are the financing aspects: you don't pay for expensive servers up front, you 'lease' them effectively - which has serious working capital benefits. All those things have considerable business value. So sure - if you want to compare only 'server instance costs' - maybe 'buying your own instance' - specifically on a server by server basis ... maybe it's cheaper to buy a server. But for most small businesses - the advantage of the cloud far outweighs the cost. I'd argue that 'rolling your own infrastructure' would be risky and costly initiative that boils down to a 'cost optimization' only, and can't really be considered until a business reaches an operational degree of maturity and visibility wherein someone could really sit down and plan quite far into the future. And even then I'm not so sure - this is why so many big and successful companies still use the cloud.
- kbenson 10y agoThere is some variance in how people interpret "cloud". Does colocating your own machine at a remote ISP constitute being in the "cloud"? What about leasing a server? What about a virtual server, but a traditional one where it's essentially no different than a single leased server? What if your multiple real and/or virtual leased servers are in the same private network at the remote location? What if there's an API available to you (even if it deploys hardware servers)? What if extra services, such as storage, can be attached? Different people will likely consider "cloud computing" to apply at different thresholds with different features. I also consider "in the cloud" (handled remotely in the internet) to be different than "cloud computing" (handled by a cloud service), and "cloud services" to me could mean either one depending on context. I find most your statements apply truthfully to what I consider "in the cloud", that is, remote hosting. I don't think they necessarily apply when used with "cloud services" platforms. All of a sudden, all the money you save not having to deal with hardware and paying someone to configure and maintain it is either back (you need someone to deal with the craziness of each cloud services platform, and they might cost more), or offset by higher costs, if you don't have a business case that requires you be able to scale later, or add network storage, etc. Better yet, if all you need is a website, there's plenty of services that do away with all that to just provide hosting of various sizing and shapes. Is that a "cloud service"? Is that a cloud service? Probably, but in a conversation about GCE and AWS, maybe it's not actually what's being talked about.