|
|
|
|
|
|
by jasonvorhe
780 days ago
|
|
|
I don't think you've shared sufficient information about your requirements to give you a good suggestion. If you're already running container workloads, DigitalOcean has a managed Kubernetes offering that's quite decent. If you're only using VMs so far, I don't think you'll gain anything by introducing the complexity of the bigger cloud providers (managing VPC, subnets, firewalling). Of course you can use a cloud provider and just stick with a common stack that can be easily moved to different providers or hosted on metal/on-prem once the need arises. In order to provide a more useful answer, I'd like to know your current tech stack and a rough estimate of traffic/users. I've done consulting for various clients who wanted to move from on-prem to cloud and vice versa and as long as you stay clear of the proprietary products you shouldn't worry that much about cloud lock-in. Stick with Postgres/MySQL, redis, containers/VMs and try to have as much of your infra in code, if possible. |
|
|
Right now, it's a simple web app + db + redis queue. We'll start with just one prod server (and a test/staging server perhaps?) with some kind of a failover setup. My goal is to keep operational complexity to a minimum. I plan to avoid k8s and just use docker compose/docker swarm/dokku.
I have seen enough places burned by going with the big 3 - either through billing, support, or the sheer complexity of managing everything. You might start of with good intentions but you tack on a service because it's easily available and the next thing you know your costs have creeped up and moving things has become a non trivial project that you don't have time for.
I am just looking for a box I can run my setup on with fair pricing, good support, and enough reputation where I have faith they are not going to fold in 6 months. And if things go south, I want to be able to migrate easily.