Slide 1

Slide 1 text

Microservices platforms: when team topologies meets microservices patterns Chris Richardson Founder of Eventuate.io Founder of the original CloudFoundry.com Author of POJOs in Action and Microservices Patterns [email protected] http://adopt.microservices.io https://www.linkedin.com/in/pojos Copyright © 2025. Chris Richardson Consulting, Inc. All rights reserved

Slide 2

Slide 2 text

Presentation goal Accelerating development of microservices by using Team Topologies Platform groups

Slide 3

Slide 3 text

@crichardson About Chris http://adopt.microservices.io

Slide 4

Slide 4 text

About Chris https://chrisrichardson.net/

Slide 5

Slide 5 text

Microservices Platforms: why?

Slide 6

Slide 6 text

Fast fl ow for business succe$$ in today’s VUCA world Development Production Continuous stream of small changes, many times a day Continuous feedback and learning Users IT

Slide 7

Slide 7 text

Organization: Enables Enables Process: Principles and practices for fast fl ow Organizational patterns for fast fl ow Fast fl ow success triangle Fast fl ow architecture: (at scale)

Slide 8

Slide 8 text

Team topologies: organizational patterns and principles for fast fl ow

Slide 9

Slide 9 text

Cognitive overload: an obstacle to fast fl ow Reduces team performance Impacts mental health: stress, burnout. DevEx Work environment than minimizes interruptions, meaningful work, … Minimize - simplify environment, automate, good documentation, … Fast feedback from colleagues, tools, deployment pipeline, production, users, … Feedback Flow Cognitive load Great https://premium.microservices.io/microservices-rules-4-provide-a-great-developer-experience/

Slide 10

Slide 10 text

Microservice architecture: two or more components Production Deployment pipeline Service Repo Deployment pipeline Service Repo Deployment pipeline Service Repo Independently deployable Loosely coupled Service Service Service Some system operations span multiple services

Slide 11

Slide 11 text

Bene fi t of Microservices: enables independent stream-aligned teams

Slide 12

Slide 12 text

Challenge: Using microservices => numerous sub- issues to resolve https://microservices.io/patterns/microservices.html

Slide 13

Slide 13 text

Implementing patterns can be challenging

Slide 14

Slide 14 text

More than patterns…

Slide 15

Slide 15 text

… more than patterns

Slide 16

Slide 16 text

Solution: Use platforms owned by platform groups

Slide 17

Slide 17 text

About platform group(ing)s

Slide 18

Slide 18 text

Bene fi ts of platforms and platform groups

Slide 19

Slide 19 text

Microservices Platforms + Teams Applicability: organizations building multiple components

Slide 20

Slide 20 text

Microservices Platforms: simplifying service creation and maintenance

Slide 21

Slide 21 text

Each service needs extensive plumbing, build logic, …

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

Pattern: Service Template https://microservices.io/patterns/service-template.html

Slide 24

Slide 24 text

Drawback: plumbing evolves => update everywhere

Slide 25

Slide 25 text

Pattern: Service chassis https://microservices.io/patterns/microservice-chassis.html Release new version Use new version Use new version

Slide 26

Slide 26 text

Propagating service template changes to the services

Slide 27

Slide 27 text

Microservices Platforms: security

Slide 28

Slide 28 text

Security architecture: authentication and authorization…

Slide 29

Slide 29 text

…Security architecture: transport-level security

Slide 30

Slide 30 text

Security platform

Slide 31

Slide 31 text

Microservices Platforms: provisioning infrastructure services

Slide 32

Slide 32 text

Services need infrastructure services

Slide 33

Slide 33 text

Solution: Infrastructure services platform

Slide 34

Slide 34 text

Infrastructure orchestrator example: Crossplane

Slide 35

Slide 35 text

Microservices Platforms: understanding application behavior

Slide 36

Slide 36 text

The need for observability Essential for reliable deployments

Slide 37

Slide 37 text

An observable service

Slide 38

Slide 38 text

About observability patterns

Slide 39

Slide 39 text

Observability platform

Slide 40

Slide 40 text

Microservices Platforms: the path from laptop to production

Slide 41

Slide 41 text

Every service has a deployment pipeline

Slide 42

Slide 42 text

Provided by a build platform

Slide 43

Slide 43 text

Microservices Platforms: deployment platform

Slide 44

Slide 44 text

Build and deployment platforms: deployment pipeline and production environment

Slide 45

Slide 45 text

Deployment platform

Slide 46

Slide 46 text

Example: Kubernetes/GitOps based deployment

Slide 47

Slide 47 text

Microservices Platforms: how?

Slide 48

Slide 48 text

https://thenewstack.io/why-up-to-70-of-platform-engineering-teams-fail-to-deliver- impact/

Slide 49

Slide 49 text

Platforms: A way to avoid addressing dif fi cult people/customer problems by diving into the in fi nity pool of technology

Slide 50

Slide 50 text

Services- fi rst, platforms-later Focus on the services, not the platforms De fi ne/evolve platforms to solve actual problems that affect multiple teams https://microservices.io/post/antipatterns/2019/04/30/antipattern-focus-on-technology.html

Slide 51

Slide 51 text

@crichardson Aim for the Thinnest Viable Platform (TVP) “Most internal platforms become bloated monstrosities that slow teams down rather than accelerate progress. The TVP approach creates platforms that provide just enough capability without unnecessary complexity. A good platform should make stream-aligned teams move faster, not generate more dependencies to manage.” WARNING ! https://teamtopologies.com/key-concepts

Slide 52

Slide 52 text

Adopt a customer-focused mindset

Slide 53

Slide 53 text

Summary: microservices require platforms…

Slide 54

Slide 54 text

…Summary: microservices platforms needed

Slide 55

Slide 55 text

Summary: apply DRY to improve maintainability Develop reusable components Libraries and frameworks Custom build tool plugins Custom CI/CD components IaC modules: Helm Library charts, … … Avoid copy/paste = code generation, large templates Provide tooling to automate updates of template instances

Slide 56

Slide 56 text

Summary: focus on the services - not technology • De fi ne platform groups that help service teams • Build minimal platforms (TVPs) that solve actual problems Focus on the services

Slide 57

Slide 57 text

[email protected] http://adopt.microservices.io Questions? https://www.linkedin.com/in/pojos