[S.A. Developer.net] - Greg Young - Applied Domain Driven Design course
Daniel Van Wyk
APPLIED DOMAIN DRIVEN DESIGN
Ever wanted to know about Command Query Separation (CQRS), Domain Events, and how to apply DDD within an organization? Then this course is for you.
Presented by renowned expert Greg Young, this course focuses on Applied DDD. This means that while the concepts will be explained, we will have a heavy focus on creating working (Java/C#) code. We will go through the different concepts and turn each concept into a working solution which you can apply without too much effort in your own domain. The group will also be small (limited to 14 seats) to facilitate interaction between course members.
To get the most out of this course, it is recommended (though not strictly required) to go through Eric Evans’ ‘Domain Driven Design -’Tackling Complexity in the Heart of Software’. This way you will have a solid basis for the more advanced topics in the course.
Click here to register for this course.
Please address your questions via email to in...@kuschkeconsulting.com.
PREREQUISITES
Basic knowledge of object modelling, design, and architecture.
RECOMMENDED
Some exposure to medium to large–scale software development in a multi–team environment. Familiarity with J2EE, .Net or other framework for large scale application development. Experience with Service Oriented Architectures is a plus. A working understanding of Domain Driven Design will help facilitate students to understand the more advanced material in the course.
COURSE OUTLINE
DAY 1 (OPTIONAL, BUT HIGHLY RECOMMENDED):
- Domain Driven Design Review – essential to the following two days
If you are extremely familiar with the DDD concepts, this day can be skipped; however, it is highly recommended you attend.
DAY 2:
Morning:
- Introduction/Outline
- User intention and why it is important
- Exercise: Building a task based UI
- Command and Query Separation
Afternoon:
- Introduction to events as a storage mechanism
- Exercise: Creating an event storage system
- Performance optimizations, snapshots
- Creation of an aggregate root that tracks its own state
Evening:
- Conext Specifications to capture intent
- How events change testing strategies
DAY 3:
Morning:
- The Read System
- Partitionability of work, developer specialization, and outsourcing
- Eventual Consistency
Afternoon:
- Organizational Sagas and the Ubiquitous Integration Language
- Versioning of the event log over long periods of time
Evening:
- Pub/Sub and building disconnected systems
REVIEWS
The previous session was done in Europe – here are some reviews: