I'm working on a new SaaS project and need to decide on the best API architecture for it. I've been building backends for around five years and have used REST quite a bit, but I also enjoyed experimenting with GraphQL recently. I've heard positive things about tRPC for type safety, although I haven't used it in a production setting yet. With all the changes in API technologies over the past few years, I'm curious about what other developers are leaning towards in 2025. What are you all using these days and what have influenced your choices? Also, I plan to use a TypeScript-heavy tech stack. Would love to hear your thoughts!
1 Answer
For me, REST with an OpenAPI schema is the way to go. It’s flexible and reliable, and you can generate client libraries based on your API definitions. Plus, the familiarity with REST means less of a learning curve for teams that are already accustomed to it. I suggest picking whatever you’re most comfortable with, especially for a commercial product.
I feel the same! REST definitely keeps things simple, and the OpenAPI docs are a lifesaver. What do you think about building the API first and generating schemas from that?