4 ms·
If you're building a B2B app: - Supabase on the backend (REST APIs are a solved problem, no need to spend a single hour on it) - Auth0 for authentication (too
by fzaninotto 4y ago
If you're building a B2B app:
- Supabase on the backend (REST APIs are a solved problem, no need to spend a single hour on it)
- Auth0 for authentication (too risky to manage authentication manually)
- react + react-admin SPA on the frontend (does 80% of the job for B2B apps)
- lambda functions (for business logic that can't be exposed on the frontend)
API-centric SPAs are such a time saver... when you don't have to build the API, and Supabase covers it.
For a B2C app, you must render server-side. I'd go with:
- Postgres
- Next.js or Remix
- Prisma
- pstorm 4y agoCurious why you suggest Auth0 and Supabase. What is wrong with Supabase auth?
- jasondigitized 4y agoWhy must you render a B2C app server side?
- fzaninotto 4y agoBecause of SEO: SPAs aren’t good at using robot time efficiently
- dinkleberg 4y agoThat is making assumptions about what type of service it is though. B2C doesn’t inherently imply that everything is public and needs to be indexable.