I will be writing more Nest.js related content soon so stay tuned! :)
Regarding your issue. It really depends on the complexity of your project. I once started a project in Nest.js with Microservices from scratch and it was really a nightmare for developers to develop it as it required many steps to even start the project. What I would suggest instead would be to go for the modular monolith which is relatively simple to create in Nest.js and considering how easy it is to refactor single Nest.js app into microservices I would highly advise that.
In summary, build a single application at first and when it will start to grow extract certain pieces of it (i.e. certain modules) into separate microservices. Thanks to that you wont be overloaded at the start of the project with too many microservices and you will scale when you will actually need it.
Hi Mor,
I am glad you liked the article!
I will be writing more Nest.js related content soon so stay tuned! :)
Regarding your issue. It really depends on the complexity of your project. I once started a project in Nest.js with Microservices from scratch and it was really a nightmare for developers to develop it as it required many steps to even start the project. What I would suggest instead would be to go for the modular monolith which is relatively simple to create in Nest.js and considering how easy it is to refactor single Nest.js app into microservices I would highly advise that.
In summary, build a single application at first and when it will start to grow extract certain pieces of it (i.e. certain modules) into separate microservices. Thanks to that you wont be overloaded at the start of the project with too many microservices and you will scale when you will actually need it.
Let me know if that answered your question :)
Hi Jakub,
Thank you for your feedback. You totally answered my questions.
Hurry to read your next article on this topic.
Have a nice day !