Domain Driven Design & Microservices for Architects
- Descrição
- Currículo
- FAQ
- Revisões
PS: Focus is on designing Microservices not coding
-
No specific Microservices framework in use
-
All sample code is in plain JAVA to demonstrate/clarify understanding of DDD patterns, etc.
-
Models are developed in UML – using the PlantUML tool
-
PostgreSQL/MongDB/RabbitMQ/Kafka – free instances created on the cloud for demos & walkthroughs
PLEASE Do NOT join the course if you are looking for tutorials on Microservices Coding or specific framework!!!
What is this course about?
Microservices is a new way of building software in which an application is composed of an independent set of services. The biggest benefit of Microservices is that it enables an organization to transform at a very rapid pace. This speed to market is achieved due to the independent nature of the services that make up a Microservices application. Companies like Amazon, Netflix and Etsy have proven the value of Microservices beyond doubt.
Many organizations today are looking to adopt Microservices. These organizations are investing in technologies, tools, skills and are changing their software development and delivery processes as well. But still many organizations are failing to achieve the full benefits of Microservices; in fact many organizations feel that they have created technical debt by adopting Microservices.
So why is it that some organizations have been successful in adopting Microservices while others are not. One common aspect I have observed in companies that fail to adopt Microservices is that they treat Microservices as a purely technology initiative. They do not spend time in understanding the business aspects of their Microservices applications !!!
Microservices is NOT just about technology
The key element of the Microservices architecture is that services are Independent. This independent aspect of the service is what makes it possible for Microservices to change independently of other services. If scope of the microservices is leading to inter-dependencies between services then it would lead to a need for change coordination between teams which in turn will lead to the same problems we have with Monolithic applications !!! Release cycles will be longer and there will be no benefit of the adoption of Microservices.
To ensure that these is no interdependencies between Microservices, a Microservices architect needs to understand the domain and then decide on the boundary and scope of the Microservices. This is where Domain Driven Design comes into picture. Once the Microservices business boundaries are defined the services should be built using appropriate Microservices design patterns and technologies.
Teams working on Microservices should not just look at the technical aspects of the service but MUST keep in mind that there are other considerations that play a critical part in the success of Microservices initiative. In order to
Role of a Microservices Architect
An IT professional working in the role of Microservices architect is responsible for may aspects depending on the maturity of Microservices adoption in their organization. Here are the list of activities that the architects is responsible for:
-
Evaluate the business benefits of Microservices for their specific organization
-
Build a Business case for Microservices
-
Educate the Business & IT stakeholders on pros/cons of Microservices
-
Apply Domain Driven Design to demarcate the boundaries of Microservices
-
Define the domain model for the Microservices
-
Do the technical design of Microservices
-
Guide and Mentor the Microservices teams
-
Evaluate the technologies | frameworks for the realization of Microservices
-
Build proof of concepts to show how things work
How will this course help?
This course will help developers & architects in building skills needed for successful implementation of Microservices applications. It consists of a combination of concepts, UML modelling and working code to demonstrate the implementation of Microservices. Students will learn the concepts of Domain driven design by way of common industry examples and a case study (ACME travels).
Focus is on Architecture, Design and Development of Microservices.
1. Transformation & Microservices
2. Domain Driven Design
3. Applying the DDD strategic & tactical pattern
4. Event Driven Architecture
5. Event Storming
6. Data Management
7. Messaging
8. Distributed Transactions
9. API
IMPORTANT:
Code Samples
Focus is on the Microservices design not coding.
-
All of the sample code is in plain JAVA
-
Course does NOT cover any specific framework
-
SpringBoot is used in samples for API/GraphQL section
Please check out the course preview lectures before enrolling the course.
-
Review the topics covered
-
Make sure you understand instructor’s accent
Pre-Requisites
-
Basic understanding of JAVA or any other programming language
-
Some experience with software development practices
PS:
Hand on part is optional but students are encouraged to do hands on tasks to get a better feel of the design patterns.
-
3
Microservices ArchitectureMonolithic Architecture
Microservices Architecture
Realization of Microservices Architecture
-
4
Business & Digital Transformation
Discussion on how Business Transformation is accelerated by Microservices Architecture.
-
5
A Business Perspective of Microservices
How teams are organized for building Microservices applications
Business capabilities and Microservices
Business Benefits of Microservices
-
6
A Technical Perspective of Microservices
Discussion on pros and cons of Microservices architecture from technology perspective.
-
7
Adoption of Microservices Architecture
-
8
Domain, Sub-Domain and Domain Experts
Understanding the domain and domain models
-
9
Conceptual models, Architecture and Design
Conceptual vs Architectural models
Architecture vs Design
-
10
Modeling techniques & Architectural Styles
Discussion on commonly used modelling techniques and Architectural styles.
Students will be introduced to Domain Driven Design in this lesson.
-
11
Domain Models
Define models and elements of domain models.
-
12
Modeling techniques & Architectural Styles
Enterprise | Unified domain models
Knowledge crunching exercise
-
13
Why understand the Business?
Overview of the topics covered in this section.
-
14
Introduction to Business Model Canvas
Understand the use of business model canvas
Learn how the Business model canvas is created
Example: Uber's Business Model Canvas
-
15
Exercise : ACME Travels Business Model Canvas
In this exercise we will create the Business Model Canvas for Acme Travels
-
16
Introduction to DDD and Patterns
Overview of the topics covered in this section.
-
17
Business Subdomain Types
Learn about the 3 types of sub domains
Core
Support
Generic
-
18
Exercise : ACME Subdomain Type Assignment
In this exercise we will categorize ACME Travel's subdomains in the core/support/generic categories.
-
19
Understanding the Business Context
Understand the meaning or Context | Business Context
-
20
Business Domain Language
Bridging the gap between Business and Technology languages. Lesson introduces students to DDD Ubiquitous Language.
-
21
Strategic Pattern : Ubiquitous Language
Discussion on characteristics of Ubiquitous Language.
-
22
Exercise : Define ACME's Ubiquitous Language
In this lesson we will develop the Ubiquitous Language terms for ACME Travels Sales subdomain.
-
23
Strategic Pattern : Bounded Context
Introduction to the DDD Strategic pattern : Bounded Context
By end of this lesson students should be able to explain the Bounded Contexts.
-
24
Discovering the Bounded Contexts in a Domain
Students will learn techniques for discovering the Bounded Contexts in a problem space.
-
25
Exercise : Identify ACME's Bounded Contexts
In this exercise we will try to identify Bounded Contexts in the ACME travels business domain.
-
26
Intro to DDD Integration Patterns
Overview of the topics covered in this section.
-
27
Managing BC Relationships using Context Maps
Big Ball of Mud
Challenges with Bounded Context dependencies
Context Maps
-
28
Symmetric Relationship Patterns
DDD Strategic Patterns:
Separate Ways
Partnership pattern
Shared Kernel
-
29
Asymmetric Relationship Patterns
DDD Strategic Patterns:
Customer-Supplier pattern
Conformist pattern
Anti corruption layer pattern
-
30
One to Many Relationship Patterns
DDD Strategic Patterns:
Open Host Service
Published Language
-
31
Exercise : Context Mapping for a Bank
In this exercise we will draw up the context mapping in a banking domain.
-
32
Intro to DDD Tactical Patterns
Overview of the topics covered in this section.
-
33
Entity Object - Pattern
DDD Tactical Pattern : Entity pattern
-
34
Value Object - Pattern
DDD Tactical Pattern : Value Object pattern
-
35
Exercise : Identify Entity & VO in ACME Sales Model
In this exercise we will identity | design the Entity and VO in the ACME Travels sales model
-
36
Hands On : Building the ACME Sales Entities & VO in JAVA
Walkthrough of the JAVA code & UML for ACME Travel Sales entities and value objects
-
37
Aggregate & Factory - Pattern
DDD Tactical Pattern : Aggregate pattern
-
38
Exercise : ACME Sales Use Case
In this exercise we will design an Aggregate in the ACME Travel Sales model
-
39
Hands On : UML for ACME Sales Aggregates
Walkthrough of JAVA code and UML model for the Aggregate(s) in the ACME sales model
-
40
Model Behavior : Anemic & Rich Models
Discussion on Anemic models and how to address anemic models
-
41
Repository Object - Pattern
DDD Tactical Pattern : Repository pattern
-
42
Hands On : ACME model Repository in UML & JAVA
Walkthrough of the JAVA code and UML model for ACME travel repository
-
43
Domain Service - Pattern
DDD Tactical Pattern : Services patterns
-
44
Application Services - Pattern
DDD Tactical Pattern : Application Services pattern
-
45
Infrastructure Services - Pattern
DDD Tactical Pattern : Infrastructure Services pattern
-
46
Hands On : ACME Domain Service, UML & JAVA
Walkthrough of the Java code and UML for the Domain Services in ACME travel model
-
47
Hands On : Application and Infrastructure Services, UML & JAVA
Walkthrough of JAVA code and UML for the ACME application and infrastructure services
-
48
Intro to Events in Microservices
Overview of the topics covered in this section.
-
49
Monolithic & Distributed Communication Patterns
Discussion of communication patterns used in Microservices
-
50
Microservices Interaction Patterns
Discussion on the Microservices interaction patterns
-
51
Event Driven Architecture
Introduction to Events Driven Architecture and its importance in development of Microservices applications.
-
52
Hands On : Pub Sub with AMQP/RabbitMQ
Walkthrough of pub-sub messaging pattern using the RabitMQ messaging broker.
-
53
Domain Events - Pattern
Introduction to domain events
-
54
Hands On : Static Class Broker Pattern
Implementing domain events with a static class broker framework pattern
-
55
Exercise : ACME Sales Domain Events
In this exercise we will Identify the ACME travel domain events
-
56
Hands On : Realization of ACME Domain Events
Walkthrough of the JAVA code and UML for the implementation of the domain events for ACME travel.
-
57
Integration Events - Pattern
DDD Tactical Pattern : Integration Events
-
58
Exercise : ACME Sales Integration Events
In this exercise we will identify the Integration Events in the ACME travel domain
-
59
Hands On : Realization of ACME Integration Events (1 of 2)
Walkthrough of JAVA code and UML for the implementation of ACME
-
60
Hands On : Realization of ACME Integration Events (2 of 2)
Walkthrough of JAVA code and UML for the implementation of ACME
-
61
Learning Objectives : Discovering the Events in a Domain
Overview of the topics covered in this section.
-
62
Introduction to Event Storming
Events storming is a technique used for creating shared knowledge of the domain. This lesson will introduce students to event storming.
-
63
Elements of Event Storming
Elements of event storming flow.
-
64
Preparing for the ES Workshop
Discussion on how to prepare for an Event Storming workshop.
-
65
Conducting the ES Workshop
The process followed in an Event Storming workshop.
-
66
Exercise : ACME Sales ES Workshop
Simulation of Event Storming Workshop for ACME sales
-
67
Introduction to Microservices Data Persistence
Overview of the topics covered in this section.
-
68
Monolithic Apps - Shared Persistence Storage
Challenges with use of Shared Database in monolithic applications
-
69
Service Oriented Architecture (SOA)
Introduction to SOA and how it addressed some of the challenges of shared database in Monoliths
-
70
Separate Database pattern
Microservices have independent persistent layer. This lesson discusses the pros of separate database pattern for microservices.
-
71
Brownfield Microservices : Database patterns | options
Option for persistence layer for brownfield applications
-
72
Shared Database Pattern
Options for breaking a shared database to separate databases
-
73
Shared Database : Challenges & Solutions
Introduction to CQRS, Event Sources and SAGA patterns
-
74
Need for more Data Patterns
Overview of the topics covered in this section.
-
75
Commands Query Separation (CQS)
Command Query Separation (CQS) Pattern
-
76
Hands On : PostgreSQL Database for backend
Setup PostgreSQL database for testing
Walkthrough of JDBC Repo implementation
-
77
Realization of Commands & Queries
Considerations for CQ pattern
Read vs Write performance
Introduction to "Collaborative Domains"
-
78
Hands On : Build the CQS Pattern
Walkthrough of JAVA code and UML for CQS realization
-
79
Command Query Responsibility Segregation (CQRS)
Discussion on CQRS pattern
-
80
Data Replication between WRITE-READ sides
Options for data replication between READ and WRITE sides
-
81
Exercise : ACME CQRS for Proposal
Exercise requires you to design CQRS for ACME Travels
-
82
Hands On : ACME CQRS command implementation
Walkthrough of JAVA code and UML for CQRS implementation
-
83
Event Sourcing and Event Store considerations
Event Sourcing pattern
Considerations for building Event Store
-
84
Hands On : MongoDB for ACME Sales READ side
Set up a NoSQL MongoDB for testing out the CQRS
-
85
Hands On : CQRS-v1 Proposal Subscriber
Walkthrough of JAVA code UML for version 1 of CQRS implementation for ACME
-
86
Hands On : CQRS-v2 Read side Query
Walkthrough of JAVA code UML for version 2 of CQRS implementation for ACME
