ES6, SCSS preprocessors, task managers, npm, etc.-nowadays, to maintain a small React-based app, you have to deal with project bundlers, test suites, CI/CD scripts, Docker configurations, and who knows what else. You may ask, if it has existed for a decade, then why is it such a hot topic only now? Mostly, over the course of the last 5-6 years, many things have undergone dramatic changes. Google was one of the first companies that adopted this approach for managing their codebases. This concept is relatively old and appeared about a decade ago. You can keep many kinds of logical apps inside one repo for example, a website and its iOS app. Keep in mind the word isolated-it means that monorepo has nothing in common with monolithic apps. Instead of managing multiple repositories, you keep all your isolated code parts inside one repository. This series is an attempt to gather and explain as much information as possible to understand how and when to use monorepos.Ī Monorepository is an architectural concept, which basically contains all the meaning in its title. There have been a lot of articles recently about why you should and shouldn’t use this type of architecture for your project, but most of them are biased in one way or another. Monorepos are a hot topic for a discussion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |