41–50 of 58 posts
No need for anything else. Vercel covers most front-end use cases, and when I need persistence/backend I have my home server. In a couple things I'll use Vercel + MongoDB Atlas so it's fully cloud, but still free. If it's something that wouldn't be free I move it to the Pi.
I used to like Linode, until I started using zfs. Their backup is not at a block level just because they can optimize it for their benefit which limits the partition be formatted only in unencrypted ext3 or ext4 to be able to use their backup service. https://www.linode.com/docs/products/storage/backups/#additi... I don't like them sweeping through list of files daily and their backup service choked having millions o…
https://fly.io and https://vultr.com I used Fly as a modern successor to Heroku (I know Heroku is still around). Features are good, scaling to 0 is great, their networking stuff is solid, and pricing is fair. I generally use it to host application backends. Vultr for when I want a long lived server or build my own infrastructure platforms. I use it as just a VPS provider for larger machines at reasonable costs. Cavea…
Hetzner, Vultr, DigitalOcean, Aeza primary: co-located server running Proxmox also cloudflare workers, cloudflare pages, github pages
So, there is an existing market of guys who know linode. If you have room in your payroll, you can hire a linode guy and have him manage it, but I would make sure that guy has a junior guy learning from him. I say this because the rest of the world either does AWS/Azure, or still does it all onsite. Just my two cents.
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 pro…
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.
I've used Digital Ocean for nearly 10 years. It's been good. That said: I don't know enough about your situation, but ... what are you optimizing for? AWS/GCP/Azure have each got a platform that provides a heap of functionality. Using that will save you time-to-delivery and engineer-hours. All the clouds have startup programs that will mean it's basically free until you get some traction. If you're looking for invest…
Don't underestimate the downside of using those "heaps of services". It was funny to see someone using RDS and was warned of expiring CA certificate and AWS suddenly charging for extended support because the version they were using went out of support period. I laughed how they were supposed to just install MySQL locally and avoided all that. If you wanted point in time recovery, just read the doc for an hour and do…
Have you considered using a provider that might help eliminate some of the operational burden of running your apps? At a very high level, when using the big 3 and hosting that's raw infra you're going to find ways to pay for _keeping things running smoothly_. At least the big three have happy paths to avoid some of the operational burden (hidden among many many foot guns). Full disclosure I work at noop.dev [1], a ho…
> the cost of avoiding is higher than the penalty of embracing This is becoming increasingly untrue with the death of ZIRP. In countries where VC money is much drier, many start-ups begin on VPS' and only move to the cloud when scalability becomes a real issue. This though, is generally frowned upon by contemporary tech culture.
This is the idea, yes. But I am hoping we can scale vertically for a long time.
My latest `serverfull` deployment: ܁ DigitalOcean droplet(s) with Docker service preinstalled. ܁ All services are running with docker-compose. ܁ Managed Postgresql and spaces for storage. ܁ Cloudflare free tier and their `tunnel` product as a reverse proxy into your docker-compose network is super useful. ܁ Github actions and container registry to compile and sync container images. We have staging/production environm…
I used to like Linode, until I started using zfs. Their backup is not at a block level just because they can optimize it for their benefit which limits the partition be formatted only in unencrypted ext3 or ext4 to be able to use their backup service. https://www.linode.com/docs/products/storage/backups/#additi... I don't like them sweeping through list of files daily and their backup service choked having millions o…
What did you switch to?