Vlad K.: DDD for architecting modular systems

Inhalt

The training includes four modules: strategic design, business logic modeling patterns and strategies, architectural and integration patterns, and balanced coupling. A module’s length is, on average, 4 hours. However, the actual length can be higher depending on the audience’s participation. All modules include interactive elements, such as quizzes, discussions, and hands-on exercises.

Strategic Design

Subdomains: Identifying boundaries and implications of the different types of subdomains Subdomains vs. Business Capabilities: Explore the commonalities and differences of the two models, applicability, and how to use business capabilities to discover subdomains.

Ubiquitous Language: Discovering and modeling domain knowledge through cultivating a shared understanding between domain experts and IT. Navigating uncharted waters: building ubiquitous languages for novel solutions in which both problem and solution domains are uncertain. Bounded Contexts: Effectively solving problems using multiple, task-oriented models. Explore the implications of bounded contexts on both technical and socio-technical design decisions

Tactical Design: Business Logic Modeling Patterns and Strategies

Business Logic: Definition, goals, and importance of a system’s business logic. Transaction Script: Implementing bullet-proof business logic that ensures correctness and consistency of the data under all circumstances. Discussed topics include concurrency management, idempotency, reliable messaging, commonly overlooked business logic implementation issues, and how to avoid them. Active Record: Extending the transaction script pattern to deal with complex data structures. Domain Model: How to tackle complex business logic with domain-driven design’s aggregates, value objects, domain events, and domain services. Event-Sourced Domain Model: Extending the domain model pattern to include the dimension of time.

Tactical Design: Architectural and Integration Patterns

Patterns of architecting individual components / services: layered architecture, ports & adapters, and CQRS. Integration patterns: Orchestrating the work of related components through designing process managers, sagas, and transactional outboxes.

Balanced Coupling

The majority prevalent software design patterns, architectures, and techniques — including domain-driven design — share the same goal: increasing the flexibility of a system by managing the coupling of its components. This module shifts the focus from specific techniques to the underlying design principles at their core. The attendees will learn what software coupling is and how it manifests itself in three dimensions: integration strength, distance, and volatility. Later, the three dimensions will be used to formulate a design heuristic for architecting modular software systems: balanced coupling. Ultimately, the balanced coupling model will be used to reinforce core principles and patterns of domain-driven design, as well as guidance for designing microservices and event-driven architecture based systems.

Der effektive Kursinhalt kann, abhängig von Trainer, Durchführung, Dauer und Konstellation der Teilnehmer:innen, von obigen Angaben abweichen.