7 ms·
Here's what the bare metal server didn't come with: API access for managing configuration, version updates/rollbacks, and ACL. A solution for unlimited schedu
by viraptor 5y ago
Here's what the bare metal server didn't come with:
API access for managing configuration, version updates/rollbacks, and ACL.
A solution for unlimited scheduled snapshots without affecting performance.
Close to immediate replacement of identical setup within seconds of failure.
API-managed VPC/VPN built in.
No underlying OS management.
(Probably forgot a few...) I get that going bare metal is a good solution for some, but comparing costs this way without a lot of caveats is meaningless.
- _xnmw 5y agoUsing cloud-managed backups can lull you into a false sense of security. I've heard enough of horror stories of the snapshot/restore mechanism failing for some reason, especially on certain edge-cases when you use huge amounts of data. What then? All your cloud marketing magic becomes a liability.
- c2h5oh 5y agoOf course there are a lot of benefits of using hosted databases. I like hosted databases and use them for both work and personal projects. What I have a problem with is: - the premium over bare metal is just silly - maximum vertical scaling being a rather small fraction of what you could get with bare metal - when you pay for a hot standby you can't use it as a read only replica (true for AWS and GCP, idk about Azure and others)
- viraptor 5y ago> when you pay for a hot standby you can't use it as a read only replica (true for AWS I'm not sure what you mean here. At least for MySQL you can have an instance configured as replica + read-only and used for reads. Aurora makes that automatic / transparent too with a separate read endpoint.
- milesvp 5y agoA hot standby is not a read replica. It's a set of servers running in a different Availability zone mirroring current prod, that is configured to automatically fail over to if the primary is offline. It's been a few years since I personally set this up in AWS, but at the time, those servers were completely unavailable to me, and basically doubled the cost of my production servers. The fact that a hot standby is usually in some sort of read-replica state prior to failing over is a technical detail that AWS sort of tries to abstract away I think.
- sciurus 5y agoThey recently announced readable standby instances. https://aws.amazon.com/blogs/database/readable-standby-instances-in-amazon-rds-multi-az-deployments-a-new-high-availability-option/ https://aws.amazon.com/blogs/database/readable-standby-insta...
- zerocrates 5y agoReadable standby instances is something AWS just recently added actually: https://aws.amazon.com/blogs/database/readable-standby-instances-in-amazon-rds-multi-az-deployments-a-new-high-availability-option/ https://aws.amazon.com/blogs/database/readable-standby-insta... Though it seems to require you to have 3 instances rather than just letting you read from the standby... I don't quite get the rationale for that.
- bingo-bongo 5y agoEven though a hot standby is technically the exact same thing as a read only replica, it solves 2 very different problems (uptime vs scaling). Personally, I never want read only queries going to my hot standby, otherwise I risk the secondary can’t handle the load in case of failover. Probably a reason like that with AWS as well, as they are selling a “hot standby” product to ensure the uptime for your RDS.
- lnxg33k1 5y agofully agree with this, in my free time I would fully go for the baremetal, but if I have to save money to a company, by placing all the headaches that are solved by AWS then I just say goodbye
- senko 5y ago> Here's what the bare metal server didn't come with: [bunch of stuff I don't need] Exactly. Imagine paying for all that when all you need is bare metal. Now imagine paying for all that just because you've read on the Internet that it's best practice and that's what the big guys do. Way back the best practice was what Microsoft, Oracle or Cisco wanted you to buy. Now it's what Amazon wants you to buy. Buy what you need.
- bushbaba 5y agoSure and you could buy a digital ocean droplet or Amazon lightsail instance for 5$/month. Both include 1TB of free data transfer.
- ozim 5y agoI am buying IaaS it is so nice to use VPS with snapshots every 4 hours that I don't have to think about. I don't care where those snapshots are stored and how much space those take. In case I need to restore my IaaS provider gives me 2-click option to restore - one to click restore and 2nd to confirm. I sit and watch progress. I also don't care about hardware replacement and anything that connects to that. I have to do VPS OS updates but that is it. I do my own data backups on different VPS of course just in case my provider has some issue, but from convenience perspective that IaaS solution is delivering more than I would ask for.
- Nextgrid 5y agoA lot of these aren’t as important for something that’s fairly static and can’t even be autoscaled or resized live (excluding Aurora - I’m talking about standard RDS). No access to the underlying OS can actually be a problem. I had a situation where following a DB running out of disk space it ended up stuck in “modifying” for 12 hours, presumably until an AWS operator manually fixed it. Being able to SSH in to fix it ourselves would’ve been much quicker.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- ReactiveJelly 5y agoSome of these strike me as things where the software _could_ exist, but it's either not FOSS, or I haven't heard of it yet. For instance, there are LVM2 snapshots. Maybe those do affect performance. If the cost difference is big enough though, couldn't you just account for that in the budget? I agree that literal "bare metal" sucks, but self-hosted with cloud characteristics (containers, virtualization) is not totally obsolete.
- freedomben 5y agoYou can get nearly all of that on your bare metal if you use something like OpenStack. I know a couple people that run vmware on home lab also.
- BirAdam 5y agoEverything has a cost. The cost of the cloud is that you’re out of control, the cloud provider owns your stuff, and a single vulnerability can make half the Earth get pwned. Whoops. EDIT: I do use cloud services for some stuff. My point isn’t being anti-cloud, just that nothing is perfect.
- pigeons 5y agoTrue, and also it costs more money.
- primax 5y agoAlso physical security, power, physical rack cost, networking, salaries to manage everything, and all those other hidden costs
- b112 5y agoThere are no "hidden costs". They're well known. Factor them all in, and "the cloud" is 1000s to millions of times more expensive than bare metal. I've seen people pay $100k/month, for services which could run on an $140/month bare metal server failover pair. Meanwhile, people still spend enormous resources managing "the cloud", writing code to deploy to the cloud, dealing with edge cases in the cloud. There are no savings, time wise, management wise, or money wise, with the cloud. You are paying for ignorance.
- gscott 5y agoI was watching a video by Neil Patel and he pays 130k a month to Aws for one website, UberSuggest. Now that is a guy with money to burn. He could put that on bare metal and use the savings to buy a hotel and food for the homeless.
- goodpoint 5y agoHidden costs? I've been in companies with their own datacenters from tiny to enormous. The costs were very clearly spelled out and always lower that SaaS. Why do people here think that cloud companies are charities? The cost of their hardware leasing, personnel, electricity, building management, insurance... it is all paid by the customer. Plus a beefy profit margin. All paid by you.
- willjp 5y agoI'm not sure, I guess it depends what you're looking for. I'm a hobbyist, with no real professional experience in server admin, so I am probably missing some important things. But most of this can be replicated with ZFS and FreeBSD jails (or on linux, BTRFS and LXC containers). >> 1. A solution for unlimited scheduled snapshots without affecting performance. You can very comfortably have instant and virtually unlimited snapshots with zfs/jails (only occupying space when files change). Very easy to automate with cron and a shellscript. >> 2. API access for managing configuration, version updates/rollbacks, and ACL. >> 3. Close to immediate replacement of identical setup within seconds of failure. There is a lot of choices for configuration management (saltstack, chef, ansible, ..). I run a shellscript in a cron job that takes temporary snapshots of the jail's filesystem, copies to a directory, and makes an off-site backup. A rollback is as simple as stopping the server, renaming a directory, and restarting it. It's probably more than a couple of seconds, but not by much. I think I'm uncomfortable exposing an API with root access to my systems to the internet, but I'm not sure how these systems work. I don't think it would be hard to set it up with flask if you wanted it though. >> 4. No underlying OS management. I don't know what this is, but I'm curious and looking it up :D. In most of the posts I'm reading here, people have really beefy rigs. But you could do this on the cheap with a 2000s era laptop if you wanted (that was my first server).
- viraptor 5y ago> You can very comfortably have instant and virtually unlimited snapshots with zfs/jails Yes, but that both requires manual scripting it and remains local to the server. Compare to scheduled RDS backups which go to S3 with all its consistency guarantees. > There is a lot of choices for configuration management (saltstack, chef, ansible, ..) Sure, those are an improvement over doing things manually. But for the recovery they can do only so much. Basically think how fast can you restore service if your rack goes up in flames. > I don't know what this is, but I'm curious and looking it up :D It means - who deals with kernel, SSL, storage, etc. updates, who updates the firmware, who monitors SMART alerts. How much time do you spend on that machine which is not 100% related to the database behaviour. I wasn't recommending everyone use RDS. If your use case is ok with a laptop-level reliability, go for it! You simply can't compare the cost of RDS to a monthly cost of a colo server - they're massively different things.
- kortilla 5y agoDon’t forget all of the outages associated with all of that crap you don’t need.
- ddorian43 5y agoIt also comes with 100x bandwidth pricing.
- znpy 5y agoThat's the point, duh. When you're using the cloud you're paying someone else a very good margin to do all of those things for you. If you do them yourself you can save quite a lot. Hardware is surprisingly cheap these days, even with the chip shortage factored in, if compared to cloud offerings.
- raverbashing 5y agoThat should cost more but not 80x more. Sure, you're paying the cost of some DBAs and SREs with that price. Still, seems too way above what it costs.
- nix23 5y ago> Here's what the bare metal server didn't come with: It's called software, you put that on top of a server, it's not some kind of magic.
- southerntofu 5y agoMost selfhosted distros have some/all of these features baked in: yunohost, freedombox or libreserver come to mind (note the latter is maintained only by a single person). "Identical setup within seconds of failure" being the exception as you need to deploy from backup which can take minutes/hours (depending on backup size) even if you have the spare hardware. Fortunately, that's the least-needed feature in your list.