Architecting for fast, sustainable flow: Enabling DevOps and Team Topologies thru architecture

In order to thrive in today’s volatile and uncertain world, businesses needs to innovate at a much faster pace. Recognizing this, IT organizations are adopting the principles and practices of DevOps and the organizational patterns defined by Team Topologies. But while DevOps and Team topologies are vital for delivering the fast flow of changes that today’s businesses need, they are insufficient. To prevent applications from becoming obstacles to rapid change, IT must also create architectures that support fast flow.

In this workshop, I describe the architectural requirements that enable DevOps and Team Topologies to deliver a fast flow of changes. You will learn about the forces that shape an architecture and the trade-offs that you will need to make when designing an architecture. I show how to decide between the monolithic and microservice architectural styles. You will learn key monolithic architecture patterns for fast flow. I describe how to design a microservice architecture.

Audience

Technology leaders, architects and experienced developers who want to learn how to use the microservice architecture effectively. The architecture and design exercises are on paper and are independent of any particular technology stack.

Format

This workshop consists of three 3 hour sessions delivered online over three days. Each session is a mixture of lectures, discussions, and exercises.

What you will learn

• Architectural requirements for fast, sustainable flow.
• The forces that shape an architecture and the trade-offs that you will need to make when designing an architecture.
• How to decide between the monolithic and microservice architectural styles.
• The key monolithic architecture patterns for fast flow.
• How to design a microservice architecture.

Outline

Day 1:
* A brief introduction to DevOps and Team topologies * Architectural requirements for fast flow * Overview of the monolithic and microservice architectural styles * How dark energy and dark matter shape the architecture * Choosing an architectural style: monolith vs. microservices

Day 2:
* The monolithic architecture pattern * Using a modular monolith for team autonomy * Minimizing build-time coupling * Accelerating the deployment pipeline * Monolithic deployment patterns

Day 3:
* The microservice architecture pattern * Service architecture vs. technical architecture * Designing a service architecture * Simplifying development with a service template and chassis * Service testing strategy

About Chris Richardson

Chris Richardson is a developer and architect. He is a Java Champion, a JavaOne rock star and the author of POJOs in Action, which describes how to build enterprise Java applications with frameworks such as Spring and Hibernate. Chris was also the founder of the original CloudFoundry.com, an early Java PaaS for Amazon EC2. 

Today, he is a recognized thought leader in microservices and speaks regularly at international conferences. Chris is the creator of Microservices.io, a pattern language for microservices, and is the author of the book Microservices Patterns. He provides microservices consulting and training to organizations that are adopting the microservice architecture and is working on Eventuate, which is an open-source microservices collaboration platform.