Sustainable Angular-Architectures with Monorepos and Strategic Domain Driven Design
Monorepos allow huge enterprise applications to be subdivided into small and maintainable libraries. This is, however, only one side of the coin: We need to first define criteria for slicing our application into individual parts and we must establish rules for communication between them.
This session looks at a solution provided by Strategic Domain-Driven Design. Using an Angular-based case study, we investigate the idea of the ubiquitous language and the bounded context, sub-domains, and context mapping. Building on this, you will learn how to implement these ideas for Angular using a monorepo. We also discuss approaches for reducing coupling between the specific parts of our monorepo.
By the end, you will have a technical solution and appropriate methodology to build sustainable Angular solutions.
Cut your application into independent sub-domains
Minimize communication and shared code between sub-domains
Organize sub-domains as libraries in a mono repo
Define access restrictions for the libraries to enforce your architecture
Trainer, consultant and programming architect with focus on Angular. Google Developer Expert (GDE) and Trusted Collaborator in the Angular team who writes for O'Reilly, the German Java Magazine, and windows.developer. Regularly speaks at conferences.