
Explore why microservice architecture over monolith improves scalability and deployment speed, define service boundaries using domain-driven design and event storming, and introduce model-based code with microservice patterns.
Explore event storming in practice, identifying events, commands, actors, and policy stickers using a customer order scenario, to map state changes and flow for a microservices architecture.
Explore event storming design for microservices, identifying aggregates, bounded contexts, context mapping, and the use of command, policy, read model, and external stickers to model orders, delivery, and inventory.
Define the design level in event storming by establishing aggregate attributes, commands, and events, and align bounded contexts with read models to guide microservice design.
Apply event storming to design read models and bounded contexts, enabling a CQRS-driven customer order query page across microservices.
This introduces explanations of microservice architecture and the advantages of microservice architecture over traditional monolithic architecture in responding to client needs.
It provides methods for designing DDD (Domain-Driven Design), which is customer-driven design at the core of microservice architecture, through event storming.
At this time, based on client requirements scenarios, event storming design practice is conducted to explain the purpose definition for each sticker and introduce how to proceed with design arrangement.
This explains event storming by dividing it into two phases: the strategic phase, which designs events (results of state changes), commands (that cause state changes), actors (subjects of actions), policies (reactions to events), read models (data that assists decision-making), aggregates (data storage), and bounded contexts (expressing limited contexts); and the tactical phase, which focuses on designing aggregate attributes, configuring command methods, and setting event triggers and attributes.
In the implementation phase, starting with understanding event storming model-based code generation, it explains fundamental theories about various microservice patterns such as Gateway, CQRS, Pub/Sub, Keycloak, and more, and provides an environment where you can actually practice these concepts.
Following the completion of all microservice pattern learning, the course covers the deployment and operations section, focusing on the essential steps for cluster deployment: packaging, dockerization, and cluster deployment. Students will learn the process of creating images using Dockerfile and the subsequent deployment procedures