Live data from Hacker News

We decided to move 90% of our workload from the cloud to on-prem infrastructure

medium.com

171–180 of 218 posts

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#171
The calculation is very thin in my opinion.

10k of infra costs are not a lot of money in a business context.

A person to operate a private cloud with OnCall, backup hardware, capacity planing etc. costs what?

I would always try to have GPU on prem as those prices are quite high bit others I would use managed.

Cloud providers are just much better in operating infrastructure ad normal ops.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#172
post #85

Earlier quoted context omitted.

How's the routing performance on that switch? I'm really struggling finding a device to fit my needs ( routing, 6-8 ports, Ethernet, at least two 2.5/5/10G).

8x 10G SFP+ with a 160GB/s full duplex backplane. So far, it has passed all of my testing with flying colors.

Isn't that only for switching? Do you use it to route, cross-vlan or similar?

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#173
post #165

Earlier quoted context omitted.

No it doesn't

Isn't it right there in the fine print? > Warranted Product is intended for consumer end user purposes only, and is not intended for datacenter use and/or GPU cluster commercial deployments ("Enterprise Use"). Any use of Warranted Product for Enterprise Use shall void this warranty. https://www.nvidia.com/en-us/support/warranty/

I must have read over that

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#174
>> "Starting a web-based or SaaS (Software as a Service) business was virtually unheard of before the age of IaaS"

> "...off-load many of its processes to an on-premise private cloud?"

On-Premise Private Cloud

I dont know why reading this my brain just cant compute. You mean you have three consumer grade computer with Dedicated GPU running 24x7?

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#175

Earlier quoted context omitted.

I hear that said a lot. I don’t think it stands. A ec2 instance or other vps requires the exact same maintenance as a bare metal server. They are essentially the same except one is virtualised and the other isn’t. The cloud actually requires more investment for large organisations. Previously you might of only had a handful of sysadmins but now you have a large dedicated platform team doing devops type work building…

> A ec2 instance or other vps requires the exact same maintenance as a bare metal server. They are essentially the same except one is virtualised and the other isn’t. Definitely not true. With a dedicated server, you need to handle backup and security yourself.

With ec2 you still need to backup. You still need to validate the backups. Security it still something you need to do since an instance is still just a VM. Same with s3 buckets etc. Google for public s3 bucket "breaches." You still need to apply patches, to configure access, to expand volumes, to configure VPCs and security groups.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#176

Earlier quoted context omitted.

Yes, they are cheap. Running one's own server is also easy peasy; far too many think it is difficult, it is not. The most expensive part is the electricity.

Easy or not, it's a job. Configuring, patching, upgrading, troubleshooting, securing, monitoring. It's only not expensive if your time is worth nothing.

And you still need to do this with an ec2 instance. Sure you can automate a lot of it via config mgmt/orchestration, but unless you're using serverless stuff on AWS, it's an awful lot like having your own VMs.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#177

Earlier quoted context omitted.

OVH has a great dedicated server offering. Definitely a great bang for the buck compared to AWS (if you can handle the downsides of course: security, backup, setup, handled by yourself).

> OVH Emphasis on backup.

And definitely keep it outside of OVH.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#178

> "Starting a web-based or SaaS (Software as a Service) business was virtually unheard of before the age of IaaS" Nonsense. There were plenty of SaaS startups. There was even a little event called the dotcom boom all about internet companies. This lack of history and experience is why new companies get into this cloud-first mess in the first place. Cloud is primarily for flexibility in iteration, dynamic scaling, or…

> Companies also vastly overestimate their scale when their entire business could probably fit on a single commodity server. Indeed, but that's completely leaving out the single most important thing: backups. With all of the major clouds, snapshots are easy to do both at a VM level and data level (e.g. RDS), and the cloud provider takes care that the backups are sufficiently spread to be disaster tolerant. In contras…

You need your own backups even if you're running EC2. If for no other reason than the vendor disappears, and you want to recreate the system elsewhere.

It's the same problem if you run your own server or on someone else's systems. You need a backup and restore plan either way.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#179

Earlier quoted context omitted.

> A ec2 instance or other vps requires the exact same maintenance as a bare metal server. They are essentially the same except one is virtualised and the other isn’t. Ani. If the hardware you’re running on is dying. In ec2 you stop it and start it. It’s on new hardware. If you run bare metal you’re screwed. Disk is dying ? Don’t matter cos your data exists multiple times over in AWS elastic storage. With bare metal y…

> In ec2 you stop it and start it. It’s on new hardware. If you run bare metal you’re screwed. You mean, you reimage? That is the slow step, you reimage, and plug the new server. Wait a bit, and your service has one more server. > With bare metal you got to shut down and replace. You take the disk out and plug a new one. You don't turn things off because of a disk. No doubt, those are costly. They are also rare (disk…

> You mean, you reimage? That is the slow step, you reimage, and plug the new server. Wait a bit, and your service has one more server.

No. When you /stop/ an EC2 instance, and /start/ it again, it moves. You do not need to reimage. This is even requested from AWS when they are having hardware failures and need to move customers off so they can decomission the hardware. They request you stop / start the instance, if you do not do it by the due date they do it for you.

> You take the disk out and plug a new one. You don't turn things off because of a disk.

If you have a storage array sure. But if you're getting bare metal hosting from a provider, you're not always getting hot swappable storage arrays.

> No doubt, those are costly. They are also rare (disk failure is less rare, but still rare).

It was 1 example, obviously there's many different hardware issues that can go wrong.

Re: We decided to move 90% of our workload from the cloud to on-prem infrastructure

#180
post #146

Earlier quoted context omitted.

> A ec2 instance or other vps requires the exact same maintenance as a bare metal server. They are essentially the same except one is virtualised and the other isn’t. Ani. If the hardware you’re running on is dying. In ec2 you stop it and start it. It’s on new hardware. If you run bare metal you’re screwed. Disk is dying ? Don’t matter cos your data exists multiple times over in AWS elastic storage. With bare metal y…

Not really If you running bare metal and have a San you can easily change what it is pointing to. Also most bare metal servers have redundancy and disks can be changed with 0 down time.

So now you're throwing a ton more money at something, costing you in purchasing the bare metal, but also the cost to maintain it. If you want to build compariable redundancy as you get with EC2 it will cost you. It wont be cheaper.
Post reply on HN