How to structure an Express.js REST API with best practices
by Davor KolencThousands of other companies use Express.js to build a REST API. How should you structure your project?
We just published this guide on our blog written by a great full-stack dev @anthonygore
If you are building an API and you are into "API-first" design, be sure to read this one :)
---------------------
So you’ve decided to join thousands of other companies and use Express.js to build a REST API. How should you structure your project?
One of the great things about Express is that it’s a very light and unopinionated framework which makes it extremely flexible in how you set it up.
A possible downside is that there isn’t much guidance on how to structure applications. This can lead to issues around maintenance and scaling.
In this post, we’ll consider some best practice approaches to structure a robust and high-performing Express REST API project.
---------------------
Why is structure important?
Why does structure matter? Why not use a “move fast and break things” approach and put your code wherever it seems to work?
Without good structure, it will become increasingly hard to understand your code and easier to accidentally break things. This means bugs increase and deployments become slower and riskier.
If you plan to scale your API the decisions you bake in earlier should support that. Otherwise, you’ll need to spend considerable time and expense rewriting your application.
Read the full blog here: https://buff.ly/3ANS5ia
