Hey everyone! I'm currently developing a productivity app that needs to be really fast—I'm aiming for response times under 200 milliseconds. However, I'm facing a dilemma between keeping my costs low and ensuring high performance. Here's the situation:
- I'm a solo developer with solid dev and DevOps skills but have a limited budget of about $20-50 per month.
- My app needs to handle real-time data syncing.
- I expect around 50-200 users at launch but want to design for growth.
My options are:
1. **Serverless (like Firebase or Supabase):** It's got easy scaling and no server management, plus some generous free tiers. However, cold starts are killing me with response times over 800ms, and I don't have as much control.
2. **VPS (such as DigitalOcean or Linode with Node.js):** This could provide consistent performance and more control, but I've faced heap errors and crashes with a 1GB droplet during load testing.
3. **Hybrid Approach:** Possibly use serverless for authentication/user management while leveraging a VPS for speed-critical APIs.
The main challenge is that I need speed but can't exceed the basic VPS tiers right now, and the 1GB limit is proving to be restrictive. I'd love to hear thoughts on whether I should stick with serverless and optimize for cold starts, try optimizing my Node.js memory usage to make VPS work, or split the workload between serverless and VPS. Any similar experiences or advice would be greatly appreciated!
5 Answers
Definitely go for a VPS, but try looking for providers like OVH or Netcup. They offer cheaper servers with great performance. You might find something that fits your needs without breaking the bank.
Scaling can be tricky without a revenue model that covers your infrastructure costs. Consider setting up cron jobs or services to ping your Supabase DB every few minutes. This could help mitigate those cold starts you mentioned, similar to a work-around. Just keep in mind, you're still paying for that processing time.
Have you thought about rewriting your Node API in Go? It could improve your memory efficiency and latency, though I know that might be overkill for what you're doing. Just a thought!
Yeah, I'm not too familiar with Go, but it's an interesting suggestion!
Honestly, 1GB might not be enough for your needs. Moving up to 2GB could resolve a lot of these issues, and as long as the cost isn't too high, it could be worth it. I'm not a huge fan of serverless architecture; it can be overhyped at times. You might want to check out Hetzner—16 euros (about 19 dollars) gets you a much larger server there. DigitalOcean's 1GB droplet is definitely under your budget cap, so you might have options to explore that you're not considering yet.
Totally agree! I find serverless appealing but prefer starting with a solid foundation. Hetzner sounds promising, thanks for the suggestion! Just hoping to avoid hitting my max budget for now.
Cold starts and VPS memory limits can be frustrating. I'd recommend starting with a small VPS, but also optimizing your Node.js setup. Running it in cluster mode (PM2 or built-in) could help utilize your CPU better and tweaking it with '--max-old-space-size' might prevent the crashes. Hetzner has affordable VPS options that could manage your traffic well if you set it up right. By the way, I'm working on a new hosting setup for developers like you that includes auto-scaling and Redis. We're in closed testing now, but wouldn't hurt to join the waitlist if you're interested!
Thanks for the tips! I’ll definitely try those optimizations.
That sounds like a clever hack! I'll look into it—kind of like redneck engineering with provisioned concurrency, right?