A Springboot developer's perspective on using TRPC

This isn't the first time I'm trying to build a SaaS. I've tried before. Looking back the tech stack that I used was perhaps a bit excessive. A quick breakdown would be as follows: Springboot NextJS Postgres Spring Security for Authentication Elasticsearch for supporting text search in documents Redis This is a bit too much. On top of using too many components in my backend, I was also kind of slowed down by using different languages for front end and backend. But we all learn. I've come back with a vengeance, the tech stack being as simple as follows: NextJS frontend NextJS server side + TRPC backend Postgres(Transactional+Vector DB) Clerk authentication Supabase as DB provider To be honest, I've loved working in T3 stack thus far. The feature that I've loved the most is the seamless transition between backend and frontend code, with end to end type safety.

Mar 24, 2025 - 18:06
 0
A Springboot developer's perspective on using TRPC

This isn't the first time I'm trying to build a SaaS. I've tried before. Looking back the tech stack that I used was perhaps a bit excessive. A quick breakdown would be as follows:

  1. Springboot
  2. NextJS
  3. Postgres
  4. Spring Security for Authentication
  5. Elasticsearch for supporting text search in documents
  6. Redis

This is a bit too much. On top of using too many components in my backend, I was also kind of slowed down by using different languages for front end and backend.

But we all learn. I've come back with a vengeance, the tech stack being as simple as follows:

  1. NextJS frontend
  2. NextJS server side + TRPC backend
  3. Postgres(Transactional+Vector DB)
  4. Clerk authentication
  5. Supabase as DB provider

To be honest, I've loved working in T3 stack thus far. The feature that I've loved the most is the seamless transition between backend and frontend code, with end to end type safety.