MSA-based design performance process

1. Deriving microservices
2. Domain identification and definition of relationships between data
3. Microservice identification
4. Definition of internal architecture
5. Establishment of MSA-based design principles reflecting organ system characteristics
6. Status analysis/microservice design based on business requirements
7. External architecture definition
8. Selection of reference model for optimal technology application
9. Optimized design for each technology element (logic/physics)
10. Capacity and cost design
11. Infrastructure capacity (container perspective) design for service construction
12. MSA-based

How to derive microservices

• There are two ways to derive microservices: decomposition by business function and domain-driven design
• Breakdown by business function
• 3Depth classification and detailed function description based on function tree
• Domain Driven Design (DDD)
• High cohesion and low coupling by decomposing services based on the lower subdomains that make up the business domain
• Domain: Business goal or smaller functional goal unit (subdomain)

Domain Driven Design

• Design meeting between developers and designers
• Complete understanding of domain and domain model before code
• Closely linking code and model
• Activities to understand and explore large and complex domains

Terminology and core content

• Bounded context
• Identifies boundaries between domains
• Ubiquitous language
• Language commonly used by project personnel
• Core subdomain
• Business Specialization
• Supported subdomains
• Optional area
• General subdomain
• Business Specialization
• Strategic Design
• Role that identifies microservices
  • As the design continues to grow, classification based on importance is necessary
  • Separate a large domain into subdomains and divide them into core, support, and general subdomains
  • Bounded context is 1:1 or 1:N
  • Find relationships between contexts and create a context map
• Design process
  1. Defining a ubiquitous language for modeling the inside of a bounded context
  2. Analyze the business and identify key concepts by analyzing the common language above
  3. Identify Bounded Context by analyzing identification concepts
  4. Create a context map by defining the mapping relationship of bounded context
  5. Analyze the effects of division and divide or integrate
  6. Microservice definition
• Tactical Design
• Event Storming
  • How to do it
    1. Find domain events
    2. Command definition and command user identification
    3. Classify domains into subdomains
• Participants: Stakeholders
  • Domain Expert
  • Analyst
  • Product Owner
  • Developer
• What you need:
  • Post-it
  • Large roll paper
• Location:
  • Large wall space without chairs
• Basic steps to follow:
  1. Domain Event (orange)
     – Attached in chronological order
     – Write in past tense sentences (eumseum font)
     – Predefine ubiquitous language to avoid using redundant or ambiguous words
  2. Process / External System (pink)
     – When a domain event calls one or more steps of a execution process
     – When linkage with an external system is required
  3. Hot spot (purple)
     – Question / Assumption / Warning / Complete if opinion collection is required
     • About domain events or processes / external systems
     • Even in cases of ambiguous required/optional values, etc., Throw
  4. Command (blue)
     – Can be API or Function unit
     – In case of batch domain event, command may not be present
     – Caused by a domain event, or may be the cause of a domain event
  5. Actor (light yellow, small post-it note)
     – Attach below command
     – user executing command (specified in ubiquitous language)
  6. The activity of dividing a domain into multiple subdomains
  7. Entity/Egret (dark yellow, large post-it note)
  8. Overlapping between command → domain event
  9. Record of object characteristics with a specific ID, or result
  achieved by command
  10. Identification of bounded context
  11. After identification, indicate whether communication between subdomains is synchronous or asynchronous
  12. Microservice identification
  13. Even in the same bounded context where functional similarities exist, functional units can be divided into small parts by dividing the parts where functional development mainly takes place and those where it does not.
• Advanced procedures:
  1. Read Model (green)
  2. User performs command data that serves as the basis for decision
  3. User Interface (white)
  4. Sketch-type screen layout
  5. Policy (light blue)
  6. Event Decision based on conditions (IF)

Insight

• Complex code is created due to non-procedural additional functions that occur during general software design