[krajzeg]

Moved backend services for my videogame from Heroku to Render. It's been super-easy, and the service is more responsive and significantly more stable now on Render, despite me paying much less.

1. Almost no work. The app was Node.js + Postgres, it stayed that way and only needed a few environment variable changes plus a database migration.

2. Almost none, I use PaaS because I concentrate on making games, and want to spend as little time touching infrastructure as possible.

3. Learned mostly that switching PaaS is not a big deal if you stick to common offerings (Postgres instead of a fancy exact-purpose-fit DB).

4. ~$100 to $27/mo

5. A Node.js app that gets rather low traffic but needs to be stable, in the 1000s of req/day. It only handles highscores/ranked mode seeds, so low requirements.

6. Would heartily recommend Render if you want to stay with a Heroku-like PaaS approach and they already support what you need.

[forgomonika]

Thanks for the info - I have some similar use cases.

How has the Postgres DB worked out for you with Render? I've been weary of using a relational DB in general since it's a single point of failure and really disruptive if your instance goes down (even with a back-up DB to failover too can be problematic if data doesn't get replicated before a crash).

Also are you just using your Node.js app as a back-end server or are you also serving web pages from it?

[krajzeg]

No issues with the Postgres - it's rock-solid so far (100% uptime over 6ish months). Most DBs are going to be a SPOF, unless you're willing to go into a distributed/replicated DB setup (which for my use case, I'm definitely not - I'd rather be down for an hour once in a blue moon).

It's an API consumed by the game client, no user-facing webpages.