Writing REST APIs by hand is a thing of the past. Frameworks like tRPC, Fastify, and Hono eliminate boilerplate with schema-driven design, improving speed and safety.

LogRocket is a frontend monitoring platform that helps developers debug and troubleshoot issues in web applications by providing session replay, error tracking, and performance monitoring capabilities. With LogRocket, developers can gain insights into user interactions, identify bugs, and optimize application performance to deliver better user experiences. Developers can learn how to integrate LogRocket into their web applications, analyze user sessions, and diagnose frontend issues effectively.

LogRocket

Modern frameworks like tRPC, Fastify, and Hono eliminate the need to write REST APIs from scratch by leveraging schema-driven design. These tools reduce boilerplate code while improving development speed and type safety, making manual API construction increasingly obsolete.

Stop Writing REST APIs From Scratch in 2025

The payoff: faster, safer, and self-documenting

Over 200k developers use LogRocket to create better digital experiences

LogRocket understands everything users do in your web and mobile apps.

This honestly sounds like whoever is reinventing SOAP with extra steps. Before SOAP was killed for REST, you used to be able to take your xsl and other schema file, toss it into wsdl, and get a full fledged endpoint implementation, no hand coding required. What killed SOAP was the lack of versioning and good update mechanics; one had to regenerate the whole library for even simple updates.

Most of the endpoints in the SaaS app I work on are not CRUD, so looking at the schema to determine the API is not going to create a “feature.”

Honestly? I had this period of being smart and using graphql, trpc, etc. But in the end they bring so much complexity and unnecessary layers that I just become tired of it. I just wanna do a feature not to manage over engineered setup. Just give me endpoint and i can write ts type myself on frontend. There weren’t real issues with managing frontend types even in medium-large apps unless you doing kind of open api but even though it fixable with adequate documentation

How is this different than writing back-end endpoints with OpenAPI/Swagger and then just auto generating the code on the front-end

<ol>
<li>Nobody writhing from scratch. Using Express !== “from scratch”</li>
<li>Fastify may be good for small projects. But where is no OOP, no ORM etc. So if u will try to implements some complex logic and/or will use DDD - u will fail.</li>
<li>if u use NestJS or NuxtJS - same. It is good to have front and SSR. But u need separate app for rest to implement complex logic. Unless u create something simple and stupid.</li>
</ol>
PS. Sounds like “Stop using complex digging machines; just use an ice auger.”