How to properly design koa2 backend microservice architecture?

Question

JavaScript

Tell me how to properly design the architecture of the koa2 backend, so that in the future it will be possible to quickly and painlessly scale and in the future these microservices will be spread over different servers, for example, Auth service on one server, and all other sections of the project too, plus if there are many developers, what would each had access only to their own microservice.
According to node, I read that in each folder you start a project with your own package.json and how to do it on koa2, because the app is essentially the same for everyone, you don’t have to make your own koa project in each folder.
I didn't find anything similar on Google, maybe there are examples?

Answer 1

It is to do separate projects. And ideally, generally distribute them to different repositories.