Domain Driven Design & Microservices for Architects

Rajeev Sakhuja

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?

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.

Enroll now

Or start a personal plan

And upskill with Udemy

What's inside

Learning objectives

Domain driven design
Architecting microservices application
Design patterns for building microservices & distributed systems
Event driven architecture

Developing api for microservices
Event storming
Develop a business case for microservices

Domain driven design
Architecting microservices application
Design patterns for building microservices & distributed systems
Event driven architecture
Developing api for microservices
Event storming
Develop a business case for microservices

Syllabus

Course Ouline

Quick intro of the instructor
Course outline
Tips to get the most out of the course

By the end of this lesson students will have the development environment setup on their local machine.

Microservices Architecture

Monolithic Architecture
Microservices Architecture
Realization of Microservices Architecture

Discussion on how Business Transformation is accelerated by Microservices Architecture.

How teams are organized for building Microservices applications
Business capabilities and Microservices
Business Benefits of Microservices

Discussion on pros and cons of Microservices architecture from technology perspective.

Adoption of Microservices Architecture

Introduction to Domain Driven Design

Understanding the domain and domain models

Conceptual vs Architectural models
Architecture vs Design

Discussion on commonly used modelling techniques and Architectural styles.

Students will be introduced to Domain Driven Design in this lesson.

Define models and elements of domain models.

Enterprise | Unified domain models
Knowledge crunching exercise

Understanding the Business Domain

Overview of the topics covered in this section.

Understand the use of business model canvas
Learn how the Business model canvas is created
Example: Uber's Business Model Canvas

In this exercise we will create the Business Model Canvas for Acme Travels

Domain Driven Design : Strategic Patterns

Learn about the 3 types of sub domains

Core
Support
Generic

In this exercise we will categorize ACME Travel's subdomains in the core/support/generic categories.

Understand the meaning or Context | Business Context

Bridging the gap between Business and Technology languages. Lesson introduces students to DDD Ubiquitous Language.

Discussion on characteristics of Ubiquitous Language.

In this lesson we will develop the Ubiquitous Language terms for ACME Travels Sales subdomain.

Introduction to the DDD Strategic pattern : Bounded Context

By end of this lesson students should be able to explain the Bounded Contexts.

Students will learn techniques for discovering the Bounded Contexts in a problem space.

In this exercise we will try to identify Bounded Contexts in the ACME travels business domain.

Bounded Context Relationships

Big Ball of Mud
Challenges with Bounded Context dependencies
Context Maps

DDD Strategic Patterns:

Separate Ways
Partnership pattern
Shared Kernel

DDD Strategic Patterns:

Customer-Supplier pattern
Conformist pattern
Anti corruption layer pattern

DDD Strategic Patterns:

Open Host Service
Published Language

In this exercise we will draw up the context mapping in a banking domain.

Domain Driven Design - Tactical Patterns

DDD Tactical Pattern : Entity pattern

DDD Tactical Pattern : Value Object pattern

In this exercise we will identity | design the Entity and VO in the ACME Travels sales model

Walkthrough of the JAVA code & UML for ACME Travel Sales entities and value objects

DDD Tactical Pattern : Aggregate pattern

In this exercise we will design an Aggregate in the ACME Travel Sales model

Walkthrough of JAVA code and UML model for the Aggregate(s) in the ACME sales model

Discussion on Anemic models and how to address anemic models

DDD Tactical Pattern : Repository pattern

Walkthrough of the JAVA code and UML model for ACME travel repository

DDD Tactical Pattern : Services patterns

DDD Tactical Pattern : Application Services pattern

DDD Tactical Pattern : Infrastructure Services pattern

Walkthrough of the Java code and UML for the Domain Services in ACME travel model

Walkthrough of JAVA code and UML for the ACME application and infrastructure services

Events Driven Architecture & Domain Events

Discussion of communication patterns used in Microservices

Discussion on the Microservices interaction patterns

Introduction to Events Driven Architecture and its importance in development of Microservices applications.

Walkthrough of pub-sub messaging pattern using the RabitMQ messaging broker.

Introduction to domain events

Implementing domain events with a static class broker framework pattern

In this exercise we will Identify the ACME travel domain events

Walkthrough of the JAVA code and UML for the implementation of the domain events for ACME travel.

DDD Tactical Pattern : Integration Events

In this exercise we will identify the Integration Events in the ACME travel domain

Walkthrough of JAVA code and UML for the implementation of ACME

Event Storming for creating shared knowledge

Events storming is a technique used for creating shared knowledge of the domain. This lesson will introduce students to event storming.

Elements of event storming flow.

Discussion on how to prepare for an Event Storming workshop.

The process followed in an Event Storming workshop.

Simulation of Event Storming Workshop for ACME sales

Microservices Data Management Patterns

Challenges with use of Shared Database in monolithic applications

Introduction to SOA and how it addressed some of the challenges of shared database in Monoliths

Microservices have independent persistent layer. This lesson discusses the pros of separate database pattern for microservices.

Option for persistence layer for brownfield applications

Options for breaking a shared database to separate databases

Introduction to CQRS, Event Sources and SAGA patterns

Microservices DB Performance Management

Command Query Separation (CQS) Pattern

Setup PostgreSQL database for testing
Walkthrough of JDBC Repo implementation

Considerations for CQ pattern
Read vs Write performance
Introduction to "Collaborative Domains"

Walkthrough of JAVA code and UML for CQS realization

Discussion on CQRS pattern

Options for data replication between READ and WRITE sides

Exercise requires you to design CQRS for ACME Travels

Walkthrough of JAVA code and UML for CQRS implementation

Event Sourcing pattern
Considerations for building Event Store

Set up a NoSQL MongoDB for testing out the CQRS

Walkthrough of JAVA code UML for version 1 of CQRS implementation for ACME

Walkthrough of JAVA code UML for version 2 of CQRS implementation for ACME

Microservices Managing the Data Integrity

As a best practice always design distributed systems for failures

Save this course

Save Domain Driven Design & Microservices for Architects to your list so you can find it easily later:

Save

Activities

Be better prepared before your course. Deepen your understanding during and after it. Supplement your coursework and achieve mastery of the topics covered in Domain Driven Design & Microservices for Architects with these activities:

Review Object-Oriented Programming Principles

Show steps

Reinforce your understanding of OOP principles, which are foundational to Domain-Driven Design and microservices architecture.

Browse courses on Object-Oriented Programming

Show steps

Review the concepts of encapsulation, inheritance, and polymorphism.
Practice applying these principles in a simple coding exercise.

Practice Identifying Bounded Contexts

Show steps

Improve your ability to identify bounded contexts by working through several practice scenarios.

Show steps

Find several case studies or business scenarios online.
For each scenario, identify the potential bounded contexts.
Justify your choices based on DDD principles.

Review 'Domain-Driven Design: Tackling Complexity in the Heart of Software' by Eric Evans

Show steps

Gain a deeper understanding of Domain-Driven Design principles by studying the foundational text on the subject.

View Domain-driven Design on Amazon

Show steps

Read the key chapters on strategic and tactical DDD patterns.
Take notes on the core concepts and examples.

Four other activities

Expand to see all activities and additional details

Show all seven activities

Review 'Building Microservices' by Sam Newman

Show steps

Expand your knowledge of microservices architecture by studying a practical guide to building and deploying microservices.

View Building Microservices: Designing Fine-Grained... on Amazon

Show steps

Read the chapters on service decomposition and communication patterns.
Take notes on the key considerations for building microservices.

Model a Domain Using Event Storming

Show steps

Apply Event Storming techniques to model a real-world domain, solidifying your understanding of this collaborative discovery method.

Show steps

Choose a domain you are familiar with, such as e-commerce or logistics.
Gather a group of people with knowledge of the domain.
Facilitate an Event Storming session to identify domain events, commands, and aggregates.
Document the results of the Event Storming session in a diagram.

Design a Microservice API using OpenAPI

Show steps

Practice designing a RESTful API for a microservice using the OpenAPI specification, reinforcing your understanding of API design principles.

Show steps

Choose a bounded context from your domain model.
Define the resources and operations for the API.
Write the OpenAPI specification using YAML or JSON.
Generate server stubs or client SDKs from the OpenAPI specification.

Write a Blog Post on Domain-Driven Design

Show steps

Solidify your understanding of Domain-Driven Design by explaining its core concepts in a blog post.

Show steps

Choose a specific aspect of DDD, such as bounded contexts or aggregates.
Research the topic and gather relevant information.
Write a clear and concise blog post explaining the concept.
Include examples and diagrams to illustrate the concept.

Career center

Learners who complete Domain Driven Design & Microservices for Architects will develop knowledge and skills that may be useful to these careers:

Reading list

We've selected two books that we think will supplement your learning. Use these to develop background knowledge, enrich your coursework, and gain a deeper understanding of the topics covered in Domain Driven Design & Microservices for Architects.

Domain-driven Design

Save

Is the seminal work on Domain-Driven Design. It provides a comprehensive guide to understanding and applying DDD principles in software development. It is highly recommended as a reference text for this course, as it provides the theoretical foundation for many of the concepts discussed. This book adds significant depth to the course material and is considered essential reading for anyone serious about mastering DDD.

Building Microservices

Save

Provides a practical guide to building microservices architectures. It covers topics such as service decomposition, communication patterns, and deployment strategies. It serves as a valuable reference for understanding the practical aspects of microservices and complements the DDD concepts covered in the course. This book is useful as additional reading to expand on the course material.

Building Microservices: Designing Fine-Grained...

Paperback

Building Microservices: Designing Fine-Grained...

Paperback

Building Microservices: Designing Fine-Grained...

Spiral-bound

$$$

Building Microservices

Kindle Edition

Help others find this course page by sharing it with your friends and followers: