CODEWITHSUNDEEP
node.jsbackend
Parham Moieni
Parham Moieni

Reputation: 81

seperating node js into parts for backend

I have built a node js app but for simplicity I made two different apps. one does the database product management job for the React frontend such as adding, updating and deleting products and the other does the authentication part with JWT token which is saved in local storage of frontend. in this way I think I'm more comfortable in managing and editing the code I wrote for them because of simplicity and small app size. should I merge the two node js app together?

I know people separate backend from frontend but it came to my mind why not separate backend into parts?

Upvotes: 1

Views: 216

Answers (1)

Dimitri Kopriwa
Dimitri Kopriwa

Reputation: 14385

It is not uncommon to have a separate service for authorization token and resource service (such as OAuth):

oauth schema

In your case, that looks like a small app, you could definitely group the two to save one process, and refactor later if needed.

If you keep them separated, you will later have less chance to mix the concerns.

You can also look at creating distributed npm features that you plug into your app (as any npm dependencies). This way, you keep things separated and modular.

In this case, you could check lerna to build a monorepo for your backend service

Upvotes: 2

Related Questions