← Back Home
Quick guide on decoupling from framework's nudged approach
I use NextJS for building a web application. It is not a blog or set of landing pages — it is more-less interactive. It has some API, client-side requests and so on, potentially can be even an Electron or React Native app.
NextJS is a remarkable framework to start. It provides countless features out of the box: perfect build system, performance optimization, routing and many others. Plus, using Vercel as hosting is a delightful experience — it provides many nice features even on the free account.
For the web application I want to keep some freedom. In case NextJS will not be the perfect match. Currently it's a full vendor lock. Which is not good for many reasons. Some of them:
These are just a few, but I believe they are important enough to play a bit safer and plan a bit more future-proof architecture for the project.
My approach is simple — keep pages as small as possible. And it is inspired by domain-driven design and layered architecture.
So, I put in page files only code that should be there. And all other code that contains business logic, goes into outside files and folders.
Let's check flow from a data/backend perspective:
With clear boundaries, I can change underlaying technologies with less friction. Not only NextJS, but also DB (currently I use Supabase) because all communication with DB is limited to
models. And I can even add new clients, like mobile apps.
From frontend side it is a similar situation:
Separating NextJS features (files for
Document) from the rest of the app.
Page Component only accepts props that needed for rendering, exposing types and unaware of the parent features. Some components down the line might use React Context created in
And I also prefer to separate UI kit layer, so it can be extracted, reused or replaced with less friction.
And my preferred folder structure is looking similar to this:
backend ⎣handlers ⎣models client ⎣components ⎣pages ⎣api pages ⎣_app.tsx ⎣posts.tsx package.json