Domain-driven design: tackling complexity in the heart of software

Table of Contents
Introduction
	Help Improve this Book!
	Trainings and Consultancy
	Thanks
Strategic Domain-Driven Design
	What is Domain-Driven Design?
	Finding Domains with Strategic Design
	Context-Mapping
	Conclusion
Implementing Strategic Design with Nx Monorepos
	Implementation with Nx
	Categories for Libraries
	Public APIs for Libraries
	Check Accesses between libraries
	Access Restrictions for a Solid Architecture
	Conclusion
Tactical Domain-Driven Design with Angular and Nx
	Code Organisation
	Isolate the Domain
	Implementations in a Monorepos
	Builds within a Monorepo
	Entities and your Tactical Design
	Tactical DDD with Functional Programming
	Tactical DDD with Aggregates
	Facades
	Stateless Facades
	Domain Events
	Your Architecture by the Push of a Button: The DDD-Plugin
	Conclusion
Short Note: Incremental Builds to Speed up Your CI Process
From Domains to Microfrontends
	Deployment Monoliths
	Deployment monoliths, microfrontends, or a mix?
	UI Composition with Hyperlinks
	UI Composition with a Shell
	Finding a Solution
	Conclusion
The Microfrontend Revolution: Using Module Federation with Angular
	Example
	Getting started
	Activating Module Federation for Angular Projects
	The Shell (aka Host)
	The Microfrontend (aka Remote)
	Standalone-Mode for Microfrontend
	Trying it out
	Bonus: Loading the Remote Entry
	Conclusion and Evaluation
Dynamic Module Federation with Angular
	Module Federation Config
	Routing to Dynamic Microfrontends
	Improvement for Dynamic Module Federation
	Bonus: Dynamic Routes for Dynamic Microfrontends
	Conclusion
Plugin Systems with Module Federation: Building An Extensible Workflow Designer
	Building the Plugins
	Loading the Plugins into the Workflow Designer
	Providing Metadata on the Plugins
	Dynamically Creating the Plugin Component
	Wiring Up Everything
	Conclusion
Using Module Federation with Nx
	Example
	The Shared Lib
	The Module Federation Configuration
	Trying it out
	Deploying
	What Happens Behind the Covers?
	Bonus: Versions in the Monorepo
	Pitfalls (Important!)
Dealing with Version Mismatches in Module Federation
	Example Used Here
	Semantic Versioning by Default
	Fallback Modules for Incompatible Versions
	Differences With Dynamic Module Federation
	Singletons
	Accepting a Version Range
	Conclusion
Micro Frontends with Web Components/ Angular Elements – An Alternative Approach
	Step 0: Make sure you need it
	Step 1: Implement Your SPAs
	Step 2: Expose Shared Widgets
	Step 3: Compile your SPAs
	Step 4: Create a shell and load the bundles on demand
	Step 5: Communication Between Microfrontends
	Conclusion
Literature
About the Author
Trainings and Consulting