English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 1h 19m | 184 MB
It’s tough to be agile if you’re working with a system that can’t handle rapid change. Domain-driven design (DDD)—one of the most effective architectural approaches for both agile environments in general and microservices in particular—can help you build systems that can stand up to change. In this course, Allen Holub provides programmers, software architects, business analysts, and product managers/owners with an overview of this essential architectural process, demonstrating how to use DDD to develop a microservice or other domain-focused system. Alan goes over the basics of DDD (and how it fits with agile), microservices, and bounded contexts and entities. Plus, he compares reactive and declarative systems and details how to approach an event storming session.
Topics include:
- How DDD differs from other architectural approaches
- How DDD fits with agile
- Advantages of microservices
- Bounded contexts and entities
- Reactive vs. declarative systems
- Using event storming to develop a DDD architecture
Table of Contents
1 Better apps with domain-driven design
2 What is DDD
3 How does DDD fit with agile
4 What is a microservice
5 Advantages of microservices
6 What are contexts
7 The ubiquitous language
8 Same name, different entity
9 Orchestrated declarative systems
10 Orchestrated reactive systems
11 What is event storming
12 The physical setup
13 Demo Events
14 Demo Activities flow
15 Demo Activities flow, part 2
16 Demo Activities flow, part 3
17 Demo Entities
18 Demo Contexts
19 Demo Context maps
20 Demo Entity maps
21 Next steps
Resolve the captcha to access the links!