That’s why as the code base grows it increases the risk of logic breakdown, responsibility leakage between the different components of the application. But in the absence of the strict architectural guidelines, the business layer does not provide specific rules to maintain responsibility boundaries between different modules and classes. Monolithic applications designed using MVC architecture have good separation between the business layer and the presentation layer. In the monolithic world, once the codebase starts growing with the growth of the business, it becomes difficult to maintain the code organized and structured as it was originally designed. So basically DDD was introduced to solve the problem of a large monolithic code base. The concept of microservices did not exist at that time. What You Will Learn Discover the DDD architectural principles and use the DDD design patterns Use the new Eclipse Jakarta EE platform Work with the Spring Boot framework Implement microservices design patterns, including context mapping, logic design, entities, integration, testing, and security Carry out event sourcing Apply CQRS Who This Book Is For Junior developers intending to start working on enterprise Java senior developers transitioning from monolithic- to microservices-based architectures and architects transitioning to a DDD philosophy of building applications.ĭomain-Driven Design (DDD) concept was introduced by first Eric Evans in 2003.ĭomain-Driven Design (DDD) concept was introduced by first Eric Evans in 2003. Here you’ll use the Axon framework as the base framework. The final set of chapters looks at what the application would be like if you used the CQRS and event sourcing patterns. To finish this section, you will examine the same microservices architecture on the Spring Boot platform. Once you have completed the monolithic application, you will walk through the complete conversion of the monolith to a microservices-based architecture, again mapping the concepts of DDD and the corresponding available tools within the MicroProfile platform (config, discovery, and fault tolerance).
By doing so, you will map concepts of DDD (bounded contexts, language, and aggregates) to the corresponding available tools (CDI, JAX-RS, and JPA) within the Jakarta EE platform. Practical Domain-Driven Design in Enterprise Java starts by building out the Cargo Tracker reference application as a monolithic application using the Jakarta EE platform. In this book you will see how these all come together in one of the most efficient ways to develop complex software. See how Domain-Driven Design (DDD) combines with Jakarta EE MicroProfile or Spring Boot to offer a complete suite for building enterprise-grade applications.
In this book you will see how these all come together in one of the most efficient ways to develop complex software, with a particular focus on the DDD process.
0 kommentar(er)
