Shawn Reisner
Jul 26, 2018 · 1 min read

My team writes a single API route per page that brings everything needed for that page with the one call. The reasoning is that it keeps the web app from becoming too chatty at the cost of building reusable routes. We have to write new code all the way from back to front each time we build a new page and it costs us an incredible amount of development time. Is this common practice because it feels like it’s the “wrong” way to build APIs. It’s an internal API if that makes a difference.

Shawn Reisner

Written by

Full Stack JavaScript Expert