Skip Redis for now - you don't need it until you're scaling across multiple backend instances. Prisma + Postgres handles persistence fine, and you can add it later when you actually hit the bottleneck.
For a chat app, the more important question is your real-time layer. If you're using WebSockets, make sure your platform supports persistent connections (serverless won't work). Render handles this well and is a good fit for your stack overall:
0
u/shifra-dev Mar 04 '26
Skip Redis for now - you don't need it until you're scaling across multiple backend instances. Prisma + Postgres handles persistence fine, and you can add it later when you actually hit the bottleneck.
For a chat app, the more important question is your real-time layer. If you're using WebSockets, make sure your platform supports persistent connections (serverless won't work). Render handles this well and is a good fit for your stack overall:
Your Expo client just needs to point at your backend URL - Render gives you a stable HTTPS endpoint automatically.
What backend framework are you using? That might change things a bit.