Hacker News Reader

Comment by slices | Hacker News Reader

Just about to set up a new app to deploy to Heroku, but this does not seem promising. Render seems like the next logical move, but curious where others are looking for alternatives.

View on HN

I moved to render years ago and have been very happy with the decision. It feels like heroku, if it never got acquired by salesforce and kept improving.

Railway for backend APIs. Render for front-end apps. That's my current go-to.

Although I would consider, _when possible_, using Vercel or Netlify.

Why/when do you use Railway over Render?

When bandwidth matters, when you don't want to over or under provision, when you need multiple seats: if you make a project with a small team, Render is going to be quite expensive because of the cost of each seat while Railway offers unlimited seats for they paid plans. Just the whole pricing is different, I found myself more leaning into Railway when doing calculations.

why split, you could use railway and render for both front end and back end

Sorry, I wasn't saying you should split, I wanted to say that depending on what type of apps you are more leaning into one makes a bit more sense than the other. Render with their own CDN is quite good for frontend apps. In comparison, the whole config and auto scalling/provisioning of Railway makes it easier for backend app.

Of course you can do both with both of these services.

Yes, Render if you want something similar.

yes,, render feels like the most natural next step right now (similar mental model). Still kind of nostalgic about Heroku, had really good times with it.

Reply on news.ycombinator.com