I need a reliable, low-cost solution for a continuous background process that runs 24/7. This process connects to a data source for real-time data handling without any triggers; it has to be always on. I'd prefer using a PaaS like Heroku but am open to VPS options if they're affordable and perform well.
Here are my requirements:
- The process must run continuously without interruptions.
- I want to keep monthly costs as low as possible.
- It should be language and runtime agnostic (Docker is fine).
- Minimal maintenance is preferred, but I'm flexible.
- Also, I need a web app or site running alongside this process.
I've looked into options like Fly.io, Render, Railway, Google Cloud Run, and Hetzner Cloud, but I'm unsure which would be best for my scenario. I'd love to hear your recommendations or any personal experiences with similar setups. Thanks!
5 Answers
Have you looked at Azure Functions? If you set it up as a durable function, you could manage long-running tasks without worrying too much about interruptions. It can be more cost-effective if you plan properly!
If your process can run in chunks, AWS Lambdas might work! They're great for tasks in short bursts and can help keep costs down under their free tier. But if you need it always running, a tiny VPS could be your best bet. Vultr has options for just $2.50 a month if you don't need too many features.
I'd recommend giving Google Cloud Run a shot. It allows for much more flexibility while leveraging Docker, plus you won't have to deal with as much maintenance as with other services. It's been a huge improvement for my ongoing processes without breaking the bank!
Consider using a DigitalOcean Droplet for around $4-$5/month. Sometimes you can even find cheaper VMs from sites like Low End Box, but just keep an eye on service quality there.
Low End Box is a great shout! I've seen some good deals there, just be ready for mixed quality.
You might want to check out scheduled GitHub Actions, which are super easy and cheap. Just a heads-up, though—they can be a bit unreliable if you need exact timing since multiple actions can run at once and preempt each other.
True! If precise timing is crucial, GitHub Actions might not be the best choice. It's worth reading up on it to understand potential issues.
Absolutely! Just be cautious with AWS's limits—they usually run up to 15 minutes, which might not suit you if you need continuous processing.