Sorry if the question has been asked before - I’ve seen a few equivalent questions but nothing similar.
I’m comparing Phoenix, Rails and Node to build an API for a client right now.
Their current backend is a Parse app with MongoDB supporting iOS and Android app and a Next.js app, so we’re purely talking about API/backend layer right now. We’d be moving out of Mongo to MySQL or Postgres.
It’s for a P2P marketplace, so the basic needs are
- authentication (including facebook login)
- payment (paypal and braintree/stripe soon)
- Probably a graphQL layer (multiple resources often required on most pages, such as users, reviews, items for sell, followers, etc on profiles)
- Deploying on aws elastic beanstalk
Almost no eng team right now (2 founders + 1 android engineer) but hiring 10-12 engineers this year (all platforms).
I’ll probably have to argue against Node since this is what they have right now. I’m debating between Rails and Phoenix with myself, as I trust Rails in being able to be good enough and make me fast as there will be gems for everything.
Are there any red flags I should be aware of with Phoenix? Something that might not be as easy as with Rails?
This is not going to be such a straight forward project as we’re talking of a rewrite + migration of backend, which is always tricky, so I wanna make sure we head the right direction, building the correct platform to support all clients and be efficient.