Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
DDD-based MSA: Event Storming Design & Microservices Pattern
Rating: 4.2 out of 5(14 ratings)
712 students

DDD-based MSA: Event Storming Design & Microservices Pattern

Event Storming Design & Microservices Pattern
Created by규수 김
Last updated 7/2025
English

What you'll learn

  • Understand event storming design techniques.
  • Learn various patterns in the microservices implementation process.
  • Understand what DDD is and be able to proceed with event storming design based on domain topics.
  • Acquire knowledge gained at each stage through AI-based microservices construction.

Course content

1 section5 lectures1h 25m total length
  • Intro - The need for MSA architecture7:54
  • Eventstorming - Event, Command, Actor, Policy13:31
  • Eventstorming - Aggregate, BoundedContext, Context Mapping, External21:53
  • Eventstorming - Design Level, Aggregate Attribute, Command Method, Event Trigger22:23

    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.

  • Eventstorming - ReadModel CQRS, Practice Extended Scenario19:53

Requirements

  • Development knowledge is preferred. Understanding of design concepts is beneficial.

Description

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

Who this course is for:

  • Students interested in microservices architecture design