Our book is free for Nrwl subscribers

Enterprise Monorepo Angular Patterns, by Nitin Vericherla & Victor Savkin.Book_EnterpriseAngularMonorepo_V3

Nrwl Technologies: Victor Savkin and Nitin Vericherla with contribution from Thomas Burleson. December 1, 2018

What's in this book?

We focus on concrete Angular development problems and how to effectively use the Nx set of power-ups to solve them.

  • Learn about the tools (such as Nx) now available.
  • Define strategies to organize your code into small single-purpose libs that can be composed to make large applications.
  • Enforce consistency across the code base with schematics that can be defined for all common tasks, restricting imports of libs to avoid common pitfalls, and more.
  • We cover Nx tools that analyze the workspace to determine the set of files that are actually affected by code changes so that we can target only these files during the build for linting, testing, and building. 

About Nrwl and Nx

We at Nrwl we use our experience working at Google to help companies build frontend applications the way Google does it.

That is why we built Nx - A set of power-ups for the Angular CLI. With it, you can implement Google-style development in your organization: you can set up monorepo development, enable code-sharing and collaboration, and use the provided tools to establish and promote best practices.

Book Excerpt

On the surface, both large and small organizations care about the same things: consistency, writing robust and maintainable code, and making changes with confidence.

What's different about large organizations is that they have hundreds of Angular engineers building dozens of apps. There is a lot of code, and this changes everything. 

While ten developers can reach a consensus on best practices by chatting over lunch, five hundred developers cannot. You have to establish best practices, team standards, and use tools to promote them.

With three projects developers know what needs retesting after making a change; however, with thirty projects this is no longer a simple process. Informal team rules to manage change no longer work with large teams and multi-team, multi-project efforts. You have to rely on automated CI process instead.