You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When multiple apps ( web app, backend or hybrid app ) are store in the single repository we call that monorepo
Monorepo embrance DRY Stands by sharing the business logic and utilites with all the apps in the that repo. Because of this we reduces the development time significantly. But poorly written code & structure can backfire this advantage.
Monorepo support multiple deployment which mean cms in the monorepo can be deployed to docker which webapp in that same repo can be deployed to amplify
When to used Monorepo?
When we develop the multiple apps ( web app, backend or hybrid app ) for an organisation with overlapping business logics.
When we want to do a development of multiple apps of an organization with managed/controlled infrastructure.
When an organisation consist of two or more apps when has overlapping business logics.
When not to used Monorepo ?
Do not use Monorepo on project with tight deadlines, a poor structure or code can reduce the quality of an app & development experience of an app over time.
Do not use Monorepo on small project. Trade off is not worth it
How about we don't share the business logic & share only utils in the Monorepo ?
Than u are not using Monorepo the right way. The goal & purpose for the Monorepo os to embrance the DRY Stands & introduce the structure of the project.
We have better approch to solve the issue of sharing utils, for that please follow this issue
The text was updated successfully, but these errors were encountered:
When to used Monorepo?
When not to used Monorepo ?
How about we don't share the business logic & share only utils in the Monorepo ?
For these sections, can u please share the articles or any source that u decided to come up with this decisions. It'll be very helpful for the others to analyze. Please share in the comment below. It'll be very appreciated.
i don't recommend the articles, because i want to prevent u guys from reading articles provided by teachers or newbie. Because most of the issue related to the mono repo are related to practices not technical.
I believe this video perfectly rounded the mono repo issue related to scaling
But still, i want u guys to reach out the connections from your dev connections ( linkedin or dev communities ) and discuss about this topic with the one who use monorepo before. By "the one who use monorepo" i mean not for fun projects or side projects. The running project with monorepo with industrial for almost a year or over the years
We are going to explore
What is monorepo?
When to used Monorepo?
When not to used Monorepo ?
How about we don't share the business logic & share only utils in the Monorepo ?
The text was updated successfully, but these errors were encountered: