Migration moves a subsystem from its current state toward a target architecture while balancing modernization effort, business value, and organizational dependencies. A subsystem may be a microservice, a monolith module, or another architectural unit. section 12.0 section 12.4
A migration strategy considers:
- Whether to run old and new versions in parallel during the transition. section 12.4
- Whether full rewriting is worth its return on investment and cost of delay. section 12.4
- How subsystem boundaries align with domains, value streams, and team structures. section 12.0
In data engineering, ETL—extract, transform, and load—is a pipeline-based integration approach. ETL pipelines can become expensive to maintain when centralized ingestion and consumption grow complex, limiting capacity for new development. section 14.1.1
Use the data-lake diagram to inspect how simplified ingestion can still produce complicated downstream access paths. section 14.1.1
