yaba101
commented
2 months ago Good point But Here is my hot take:
- tRPC is based on Tanstack query so instead of add more complexity to the app, we can use Tanstack query + zustand for data fetching layer
- For the mutation staff Tanstack Query + Server action
- even if app router have RSC, In my opinion using Tanstack query ( support server hydration ) for data fetching is lot better than RSC
Proposal for using TRPC
By using TRPC for the API we can define our API endpoints as TypeScript functions, eliminating the need for separate API documentation and ensuring type-safety across the entire stack.
Adopting tRPC would bring the following benefits:
Type-Safety: tRPC leverages TypeScript's type system to ensure that the data structures used in the front end and backend match, reducing the risk of runtime errors caused by type mismatches. Efficient Communication: tRPC uses RPC (Remote Procedure Call) pattern, which allows for more efficient communication between the frontend and backend, reducing over-fetching and improving performance.
Better DX: tRPC provides a better developer experience with features like automatic code generation, TypeScript intellisense, and better tooling support.