The evolution of Domain-Driven Design (DDD).
In 2004, Eric Evans completed Domain-Driven Design Tackling Complexity in the Heart of Software, proposing a methodology and philosophy for modeling business domains— domain-driven design, or DDD for short.
DDD can be said to be a methodology, a solution to how complex software can quickly respond to various changes.
DDD continues to evolve and has gone through three main stages over the past decade:
* The first is the creation and popularization of Eric Evans' theoretical principles;
* Followed by the introduction of domain events, event traceability phase;
* Finally, the proposed phase of the microservices architecture.
Since the boundary context proposed by DDD has clearly demarcated the boundaries of the business, the implementation of microservices is logical. Of course, the popularity and development of microservice architecture has also rapidly promoted the popularization and development of DDD.
The Cargo Tracker Application is a classic example of DDD: based on the DDD hierarchical architecture and the CQRS architecture (Command Query Responsibility Segregation), the Spring Boot microservices framework, RabbitMQ message middleware and Spring Cloud Stream components are adopted Data JPA and other technology stacks.
The technical column of "DDD Domain Driven Design - Cargo Transport System" starts from the actual battle to help developers quickly grasp the modeling methods and microservice application development of the DDD field.
