Build Microservices that accelerate delivery, not slow it down
Many teams adopt microservices with the goal of moving faster, but end up with a distributed monolith: fragile, tightly coupled services that change in lockstep and slow down both delivery and innovation. The result? Frustrated teams, rising costs, and delayed value for customers.
When applying the microservice architecture pattern, the most important design decisions you make are not about technology choices, Kubernetes vs. Serverless, or REST vs. gRPC. What really determines success is designing an architecture that supports fast flow: the continuous delivery of valuable changes to customers.
To achieve this, you must identify services correctly and define their responsibilities, APIs, and collaborations. Poorly designed services turn into hidden points of failure, forcing teams to coordinate every change and recreating the same bottlenecks of a monolith, only distributed.
In this three-day Designing Microservices Workshop, you’ll learn how to design a loosely coupled, resilient architecture that enables fast, sustainable flow of value. Through lectures, hands-on exercises, and real-world design reviews, you’ll gain practical skills to avoid common architectural anti-patterns and build microservices that scale with your teams and your business.
Join Chris Richardson to learn proven techniques for designing successful microservice architectures.
The Trainer 
Chris Richardson is a software architecture consultant and the author of the book Microservices Patterns.
He founded the original CloudFoundry.com, an early Java PaaS for Amazon EC2. Today, he is a recognised thought leader in microservices, and he helps organisations deliver better software faster.
Learning Objectives
- Understand when to use the microservice architecture
- Identify and define services
- Design operations that span multiple services using patterns such as Saga and CQRS
- Evaluate a microservice architecture and identify architectural smells
- Refactor and improve the architecture
- Document a microservice architecture.
Target Audience
This workshop is for you if you’re an experienced developer, architect, CTO, or VP of engineering, and you are either using or planning to use the microservice architecture.
If you are considering migrating your monolith to microservices, you will learn how to avoid many pitfalls using the microservice architecture pattern. Alternatively, if you are currently using microservices, you will learn how to improve your microservice architecture now and in the future.
Topics
- The architectural requirements for fast, sustainable flow
What DevOps and Team topologies require from the architecture in order to deliver a continuous stream of small changes, - Dark energy and dark matter, the forces that shape an architecture
The conflicting concerns, such as increasing team autonomy by defining smaller services vs. the need for efficient inter-service communication – that you must address with designing an architecture, - The essential characteristics of the microservice architecture
A precise definition of this architecture style, including its essential features, why it enables fast flow, and why it doesn’t mean a collection of tiny services, - A process for designing a microservice architecture
A rigorous design process for creating an architecture that carefully balances the dark energy and dark matter forces, - Eventually consistent service collaboration patterns
Eventually consistent patterns for implementing requests that span multiple services.
Agenda
Through a combination of lectures, discussions, and kata exercises, the trainer, Chris Richardson, will walk you through distilling your application’s requirements into a collection of loosely coupled, appropriately-sized services.
Day 1
- Designing a microservice architecture for fast, sustainable flow
- Discovering system operations
- Designing subdomains.
Day 2
- Service collaboration patterns
- Designing a service architecture, part 1.
Day 3
- Designing a service architecture, part 2
- Evaluating a microservice architecture
- Refactoring a microservice architecture.
How it works
In this workshop, you will design a service architecture for a simple, yet realistic application.
The workshop is a mixture of Lectures + Katas + Design reviews.
We’ll use a variety of tools, both tech and non-tech, such as Miro, pen and paper, post-its, for all the exercises.
The workshop will mix of theory and practice, with lots of practical exercises, both solo and in groups.
F.A.Q.
Do I need to know something beforehand to participate in this workshop?
You’ll get the most out of this workshop if you already have experience in developing enterprise applications.
What languages will be used throughout the workshop?
The architecture and design exercises are on paper or Miro, therefore they are independent of any particular technology stack.
There won’t be any code-based exercises.
Do I need my laptop to attend this workshop?
Yes. Participants will decide whether to do the design exercises on paper or using technology such as Miro.
We won’t be doing coding exercises during the workshop.
Will there be any materials to take away?
Yes, slides and design template documents.
