[crcastle]

In addition to what cpursley said in a sibling comment:

- http/3 (and 2)

- DDoS protection

- Mount a disk if you need persistent storage across deploys

- Secrets files (not just env vars)

- Private networking and DNS-based service discovery between your account's deployed services

Disclosure: I'm a Render Dev Advocate

[w-ll]

I've seen Render.com pop up a lot lately on HN. Even have a pinned tab for the migration from Heroku to Render. I have some work stuff on both Heroku and EC2 (gpu instances) and a lot of side projects between both. That said I have a few questions if you dont mind.

First is there anything you think that Heroku is still better at then Render is today? Not including stuff thing might come later, but if I had to use todays stack.

I see some locations/regions but would like to know more about where the datacenters are, and how close to AWS networks they are.

What tuning options do I have for Postgres and Redis.

Thanks!

[jvergeldedios]

I really like the pipelines feature in Heroku. Being able to automatically deploy to a staging environment from main and then be able to promote that exact slug to production is pretty cool. I’ve yet to find a tool that has replicated that experience or something like it without getting in the weeds with Docker.

As far as I know it’s not possible to have separate environments where you’re guaranteed a bit-for-bit match going from staging to production in Render. You have to build for each environment, which if your builds are deterministic should be fine, but I’ve definitely seen that go haywire where you find out your build is in fact not deterministic in some subtle way.