In this session, we'll explore a case study on how to use proven domain-driven design principles to make the architecture of your Angular project maintainable in the long term and how to combine these ideas with best practices from the community.
In this session, we'll explore a case study on how to use proven domain-driven design principles to make the architecture of your Angular project maintainable in the long term and how to combine these ideas with best practices from the community.
In this interactive session, we'll explore a case study on how to use proven domain-driven design principles to make the architecture of your Angular project maintainable in the long term and how to combine these ideas with best practices from the Angular community. First, we define a strategic and tactical design for the case study, which we'll then implement with a monorepo that reflects our sub-domains. Then, you'll learn in individual demonstrations how the use of libraries, APIs, facades, domain events, and access rules between libraries can ensure loose coupling and, thus, better maintainability.
OpenCourser helps millions of learners each year. People visit us to learn workspace skills, ace their exams, and nurture their curiosity.
Our extensive catalog contains over 50,000 courses and twice as many books. Browse by search, by topic, or even by career interests. We'll match you to the right resources quickly.
Find this site helpful? Tell a friend about us.
We're supported by our community of learners. When you purchase or subscribe to courses and programs or purchase books, we may earn a commission from our partners.
Your purchases help us maintain our catalog and keep our servers humming without ads.
Thank you for supporting OpenCourser.