Development Process

What is it?

A document that introducing on how I construct a large scale system in terms of domain-driven design. The fundamental structure of the whole development process is based on domain-driven design (DDD) and system-design-primer. DDD provide a organized and clear way to break down problem into actual tactical context, while system-design-primer demonstrate a solid and comprehensive frame and details that including merit and demerit of apply any component into a system and what is the potential alternatives.

Table of contents

• Check Business Idea
• Strategic Design
  • Problem Space
    • Identify full end-to-end business use case
    • System Context Diagram
    • Domain Design
  • Solution Space
    • Build Bounded Context based on problem space in domain model
    • Build Bounded Context Map
    • Define Ubiquitous Language in Bounded Context
    • Identify Use Story through Event Storming
    • Identify User Story in Bounded Context in terms of role/permission based on UseCase
  • User Story and Worker
    • User Story
      • Stock Catalog Context
      • Customer Self Context
      • Customer Identity Context
  • User Story and Operation/Transaction
    • Customer can search stock based on ticker/name
    • Customer can login to check their dashboard, User can change his profile and setting and delete his account
• Tactical Design
  • Infrastructure Strategy
    • 1. Constraints and assumptions
      • State assumptions
      • Calculate Read/Write usage
    • 2. System Design: InfraStructure
      • Service Mesh Pattern
    • 2.1 Infrastructure - Traffic
      • North-South Traffic Management
      • West-East Traffic Management
    • 2.2 Infrastructure - Security
      • Authentication/Authorization Flow
    • 2.3 Infrastructure - Service-Level (Sidecar)
    • 2.4 InfraStructure - Monitoring
      • Metrics
      • Tracing
      • Logging
    • 3. Scale the design
      • Infrastructure scale
      • DB scale
      • Cache
  • Contexts
    • Stocks (Core domain)
    • Identity (Supporting domain)

Check Business Idea

Check other products' pros and cons in order to understand which direction I can head on and how many rooms of opportunity I can have. Details discussions are not listed here since PM is not my career goal. Nevertheless, I did explore and do some research in advance.

Strategic Design

Ref: https://ithelp.ithome.com.tw/m/articles/10216792

Main objective of DDD is to define Bounded contexts, the Ubiquitous Language and the Context Maps together. They help me to identity the relation between problem I have faced and solution I can apply. Not only leveraging from DDD, but I also take advantage of use-case and user story. All the tools I have can really help me to build a large scale system from scratch. To be more specific, from use-case to functional program.

Check more details in Strategic Design

Tactical Design

Ref: https://ithelp.ithome.com.tw/m/articles/10216792

In addition to simply applying tactical design in DDD, I merge the structure of system-design interview into my own version of "tactical design".

Generally, every decision are accompany with tradeoffs and alternatives. I will list them all in each stage and explain why a choice is the best for me. Since the other options are ready there, I can quickly migrate from current setup to others based on observations that are mainly from system metric from time to time. The topics contain key point of a system, e.g. core component and scale strategy.

Check more details in Tactical Design

License

GNU GPL This document should be used as reference in my future interview and this purpose only.