91–100 of 268 posts
Earlier quoted context omitted.
In fact, if you're using Linux on your workstation you'll use the same skills locally as you do on the VPS/bare metal (depending on your scale.) Arguably "cloud" services need more sysadmin skills, not less.
It's far easier to maintain my own Linux workstation than an internet-facing server used daily by customers.
Yes. I once did zero downtime migration first from AWS to Google, then from Google to Hetzner for a client. Mostly for cost reasons: they had a lot of free credits, and moved to Hetzner when they ran out. Their savings from using the credits were at least 20x what the migrations cost. We did the migration by having reverse proxies in each environment that could proxy to backends each place, set up a VPN between them,…
Would you have a write up in more detail of what you did, even high level. Seems cool thing to do
Moved from Google Cloud -> Digital Ocean -> OVH. Running our own stuff on high powered servers is very easy and less trouble than you think. Sorted out the deploy with a "git push" and build container(s) meant we could just "Set it and forget it". We have a bit under a terabyte of Postgresql data. Any cloud is prohibitively expensive. I think some people think that the cloud is as good a sliced bread. It does not rea…
> Really, I can't see a compelling reason to be in the cloud for the majority of mid-level workloads like ours. I work on a very small team. We have a few developers who double as ops. None of us are or want to be sysadmins. For our case, Amazon's ECS is a massive time and money saver. I spent a week or two a few years ago getting all of our services containerized. Since then we have not had a single full production…
Earlier quoted context omitted.
Interesting - we moved the other direction (to Linode) from Rackspace because their VM/dedicated pricing was just out of whack. Our new box was nominally the same as the old at half the price, but the "4 CPU" was so much newer that it was nearly 2x.
At the same scale? I guess if you move a whole data center, they'll quote very different prices from their public ones.
The SaaS tool was mostly cloud-agnostic, so the changeover was not terrible. Changing the deployments to use DO's CSI storage, setup secrets, deploy services. I stood up the entire infra on DO, then moved the DNS over one subdomain at a time.Took about 4 days to make the move, including validating everything, and finally cutting off Linode totally.
Earlier quoted context omitted.
Yes, but what about the million new customers you're going to get next week?
Funny, but honestly, a single dedicated server should easily be able to handle a million users, for most CRUD apps.
Earlier quoted context omitted.
> None of us are or want to be sysadmins. It's such a huge misconception that by using a cloud provider you can avoid having "sysadmins" or don't need that kind of skills. You still need those, no matter which cloud and which service you use.
In fact, if you're using Linux on your workstation you'll use the same skills locally as you do on the VPS/bare metal (depending on your scale.) Arguably "cloud" services need more sysadmin skills, not less.
I have yet to work with a $corp that uses Linux for workstations.
Overwhelming majority uses Windows. Some use macOS.
The ocasional developer that uses linux will usually be in a VM, or if IT policies allow, WSL.
So yeah, running cloud services doesnt require sysadmin skills, unless you assume copy pasting from oficial documention "sysadmin skills".
I mostly use only basic services so pretty much any cloud provider can fit my use case. It took some time but I have peace of mind now.
Earlier quoted context omitted.
Why did you feel IBM is best when you only use K8S? Our platform fully K8S and I'm looking to somewhere where we get more performance per buck, probably not IBM but I'm surprised it's even in the list. Do they have an extra nice K8S dashboard or something?
Not sure where you're currently at and considering moving to, but GKE has been much simpler than EKS. Not sure about cost but it'll likely save some operations time (auto scaling is a single check box, no IAM, scaling controllers, etc)