Tagged articles
tactical design
26 articles · Page 1 of 1
This article presents a comprehensive software design methodology spanning strategic design (bounded contexts, domain partitioning, architectural style selection), tactical design (functional and non-functional modeling), structural modeling (class responsibilities, package structure), behavioral modeling (sequence diagrams, state machines), and DFX (design for performance, reliability, cost) — with concrete code examples and real-world failure patterns.
Bounded ContextCircuit BreakerSaga pattern
0 likes · 34 min read


ZhiKe AIJun 2, 2026 · Backend Development
The article argues that Domain‑Driven Design is not an architectural style but a two‑layer framework—strategic design defines bounded contexts and ubiquitous language, while tactical design supplies the modeling tools—explaining common misreadings and showing how DDD complements Clean, Hexagonal, CQRS, and Event Sourcing approaches.
Bounded ContextStrategic Designaggregates
0 likes · 14 min read

This article explains why domain models are needed, walks through DDD's strategic and tactical design concepts, demonstrates a full knowledge‑payment platform case with bounded contexts, aggregates, and ubiquitous language, and outlines practical guidelines and limitations for applying DDD in real projects.
AggregateStrategic Designdomain-driven design
0 likes · 10 min read

This article explains how detailed design documentation, the distinction between strategic and tactical design, and the CRC (Class‑Responsibility‑Collaborator) method together form a flexible, evolving blueprint that guides development without over‑prescribing implementation details.
CRC cardsStrategic Designdocumentation
0 likes · 6 min read


JavaEdgeAug 23, 2024 · Backend Development
This article delves into the tactical design of Domain‑Driven Design, explaining core building blocks such as entities, value objects, aggregates, domain events, repositories, application services, and domain services, and shows how they help keep business logic centralized and expressive.
AggregateApplication ServiceDDD
0 likes · 9 min read

This article explains how Domain-Driven Design (DDD) can be used to tackle the complexity of a B2B marketing system by detailing strategic design, tactical design, and code architecture practices, illustrating concept modeling, bounded contexts, aggregation roots, and layered architectures with real‑world examples and diagrams.
Strategic Designdomain-driven designtactical design
0 likes · 18 min read

This article explains how Meituan applied Domain‑Driven Design to build a scalable B‑side marketing platform, covering background challenges, core DDD concepts, strategic use‑case modeling, tactical code mapping, aggregation design, and practical architectural patterns for large‑scale systems.
DDDStrategic Designcode architecture
0 likes · 20 min read

This article explains Domain‑Driven Design (DDD) from its origins to practical modeling, compares it with MVC, outlines business and personal benefits, discusses drawbacks, details strategic and tactical concepts, and walks through a real‑world VOC product example using event‑storming and four‑color modeling.
DDDStrategic Designdomain-driven design
0 likes · 34 min read

This article walks through the application of Domain-Driven Design (DDD) in a B‑side marketing platform, detailing how strategic design defines use cases and unified language, tactical design maps concepts to object models, and code architecture organizes implementations, illustrated with concrete examples, diagrams, and practical guidelines.
B2B MarketingStrategic DesignUnified Language
0 likes · 20 min read

Domain‑Driven Design aligns software architecture with business needs by establishing a shared language, clear bounded contexts, and strategic‑tactical patterns—entities, value objects, aggregates, services, and events—while using techniques such as Event Storming and Four‑Color Modeling to visualize domains, guide micro‑service boundaries, and produce maintainable, adaptable systems.
Strategic Designdomain-driven designmodeling
0 likes · 28 min read

This article explains the fundamentals of Domain‑Driven Design, distinguishes strategic from tactical design, outlines core DDD elements such as domains, aggregates and bounded contexts, and demonstrates how four‑color modeling can be applied to real‑world e‑commerce microservice architectures.
DDDStrategic Designdomain-driven design
0 likes · 11 min read

This article explains how Domain‑Driven Design can guide the splitting of monolithic applications into well‑structured microservices by introducing DDD fundamentals, strategic domain modeling, tactical design patterns, and a concrete Go code example that demonstrates a four‑layer architecture.
DDDStrategic Designbackend development
0 likes · 14 min read

This article explains the core concepts of Domain-Driven Design, why it is needed to address typical development problems, and how its strategic and tactical practices—such as bounded contexts, ubiquitous language, aggregates, and domain events—help teams build clearer, more maintainable software systems.
Event StormingStrategic Designdomain-driven design
0 likes · 15 min read

This article explains the origins of Domain‑Driven Design, describes strategic concepts such as domain, bounded context and context mapping, explores tactical building blocks like entities, value objects, services, aggregates and factories, and demonstrates practical architecture choices and Java code examples for a payment system.
JavaStrategic Designarchitecture
0 likes · 31 min read

This article introduces Domain‑Driven Design, explaining its strategic and tactical aspects, core concepts such as bounded contexts, ubiquitous language, aggregates, entities, and value objects, and illustrates how DDD can be applied to complex business domains like hotel transaction systems.
Bounded ContextStrategic Designdomain-driven design
0 likes · 17 min read

This article walks through Domain‑Driven Design fundamentals, distinguishes strategic and tactical design, introduces the four‑color modeling archetypes, and demonstrates their application in an e‑commerce microservice case study, highlighting how DDD bridges business requirements and code architecture.
Bounded ContextDCI ModelingFour-Color Modeling
0 likes · 14 min read

This article summarizes Evans' concise DDD booklet, explains why domain‑driven design is needed, outlines the problems it addresses, describes strategic and tactical design practices—including bounded contexts, ubiquitous language, aggregates, and event storming—and highlights common pitfalls and supporting tools.
Event StormingStrategic Designdomain-driven design
0 likes · 15 min read

This article explains Domain-Driven Design (DDD), outlining why it is needed, how it solves common software development problems, and detailing strategic and tactical design steps, event‑storming techniques, and common misconceptions to help teams align business and technical perspectives.
Bounded ContextEvent StormingStrategic Design
0 likes · 14 min read

The article explains the rise of Domain-Driven Design, its strategic and tactical design aspects, and how it helps define business boundaries to solve microservice decomposition challenges, providing a step‑by‑step approach for architects transitioning from monolithic to microservice systems.
DDDStrategic Designdomain modeling
0 likes · 11 min read

The article explains how Domain-Driven Design (DDD) rose to prominence by addressing business‑boundary challenges in microservice architectures, outlines the evolution of software architectures, and details DDD’s strategic and tactical design practices for creating clear, maintainable service boundaries.
DDDStrategic Designdomain-driven design
0 likes · 9 min read

This article explains how to design a stable and high‑performing software architecture by addressing strategic principles—suitability, simplicity, evolution—and tactical guidelines for high concurrency, high availability, and business‑oriented design, while illustrating logical and physical architecture diagrams.
Design PrinciplesStrategic Designhigh concurrency
0 likes · 15 min read

This article explains how Domain‑Driven Design (DDD) gained popularity alongside microservices, outlines the evolution of software architectures, highlights the boundary‑defining problems of microservices, and shows how DDD’s strategic and tactical design methods help create clear, high‑cohesion, low‑coupling systems.
Strategic Designbackend developmentdomain-driven design
0 likes · 10 min read

This article explains the principles and benefits of Domain-Driven Design (DDD), describing how strategic and tactical design, layered and hexagonal architectures, CQRS, and bounded contexts help manage complex business logic, improve scalability, and align software development with evolving business requirements.
Strategic Designcqrsdomain-driven design
0 likes · 40 min read

This article explains how the evolution from monolithic to microservice architectures created a need for clear business boundaries, why Domain‑Driven Design (DDD) has become popular, and outlines its strategic and tactical concepts, practical steps, and its relationship with microservices.
Strategic Designtactical design
0 likes · 11 min read

Domain-Driven Design (DDD) has surged in popularity as microservices dominate, and this article traces its historical background, explains the architectural shifts that created its need, outlines strategic and tactical design concepts, and provides a three‑step method for defining domain models and service boundaries.
Strategic Designdomain-driven designmicroservices
0 likes · 10 min read

This article explores how Domain-Driven Design (DDD) can address the growing complexity of business and technical requirements in large-scale systems, detailing its strategic and tactical processes, layered and hexagonal architectures, and integration with microservices to achieve flexible, maintainable, and scalable software solutions.
Strategic Designdomain-driven designhexagonal-architecture
0 likes · 42 min read
