Why I stopped using REST for side projects

TL;DR

TRPC offers efficient RPC-style communication between frontend and backend, enhancing type safety and usability.

Transcript

all right so i wanted to do a little talk about why i've decided to kind of embrace trpc and just use this as my communication layer between my front and my back end um i've been watching a lot of theo and he kind of introduced me to this stack create t3 app he's another youtuber and a twitch streamer so check him out he has a lot of good informati... Read More

Key Insights

• 😣 TRPC simplifies backend communication by allowing direct function calls, which reduces complexity compared to REST APIs.
• 👨‍💻 TypeScript integration is crucial for ensuring type safety, thereby enhancing code reliability across the application stack.
• 💱 The ability to make immediate changes in backend functions and receive instant feedback in the frontend is a game-changing aspect of using TRPC.
• 😣 Developers moving from REST to TRPC can experience a significant reduction in boilerplate code, resulting in a cleaner and more maintainable codebase.
• 😣 TRPC's structure is particularly beneficial for internal applications, where traditional REST endpoints may be overly complex or unnecessary.
• 👻 The integration with tools like React Query enhances the data-fetching experience, allowing for more robust applications without additional complexity.
• 😄 The speaker encourages developers to explore TRPC's documentation for setup guidance, but emphasizes the ease of integrating TRPC into existing projects.

Questions & Answers

Q: What is the primary advantage of using TRPC over traditional REST APIs?

The primary advantage of TRPC is its ability to simplify the communication layer between frontend and backend. It allows developers to call functions directly rather than navigating RESTful endpoints, thereby streamlining the development process and reducing boilerplate code. TRPC's structure makes internal services easier to manage, particularly for applications without public APIs.

Q: How does TypeScript enhance the developer experience when using TRPC?

TypeScript enhances the developer experience by providing type safety between the frontend and backend. This means that errors related to incorrect data types or missing parameters are caught at compile time rather than runtime. This immediate feedback significantly decreases debugging time and increases code reliability, allowing developers to resolve issues more efficiently.

Q: Can you provide an example of how TRPC improves interaction between the frontend and backend?

A notable improvement is seen in how developers can call backend functions, such as deleting an image. Instead of crafting RESTful endpoints, developers use a simple call like images.delete, passing required parameters directly. If there's a change to the backend function that requires additional parameters, TypeScript flags this error in the frontend immediately, ensuring accurate interactions.

Q: What role does IntelliSense play when using TRPC with TypeScript?

IntelliSense plays a critical role by providing real-time feedback and suggestions within code editors. When developers integrate TRPC in their projects, they benefit from IntelliSense, which automatically retrieves available queries, mutations, and parameter requirements directly from the code. This reduces reliance on external documentation and enhances coding efficiency.

Summary & Key Takeaways

• The speaker discusses their transition from REST APIs to TRPC as an API solution, emphasizing the advantages of remote procedure calls for better backend function accessibility.

• They highlight the benefits of using TypeScript with TRPC to ensure type safety between the frontend and backend, reducing errors and improving debugging.

• The speaker mentions additional features of TRPC, like IntelliSense support in code editors, which aids developers in quickly identifying available endpoints and required parameters, streamlining the development process.