The CDK monorepo model

You are probably familiar with the concept of monorepos. The details are outside the scope of this book, but essentially, monorepos point to all code and assets of a certain project, client, or company being in a single GitHub repo as opposed to logically separating the code by, for example, separating the frontend and the backend of the code base into different repositories.

There are many upsides and downsides to using monorepos, and developers use them at varying levels for code organization, from keeping the entire company code within a repo to just storing project-specific code in a single repository. For example, at Westpoint, we like to keep each client’s code in a separate monorepo within a separate GitHub organization. This way, we keep things secure and easier to configure.

But if you have different levels of developer access to different bits of your organization’s code, it’s best to use other methods. We aim to keep things...