Skip to content
0:00 / 0:00

#teamtopologies#cognitiveload

Monoliths vs Microservices is Missing the Point—Start with Team Cognitive Load - Team Topologies

IT Revolution

15K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Matthew Skelton, co-author of Team Topologies
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

156K views7 years ago2 recommendations

Software designTools and practiceSoftware architectureCode review and teamworkMicroservices and monoliths

Matthew Skelton and Manuel Pais explain how to organize software teams around cognitive load rather than technology choices.

DOES19 London — The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk, we explain how and why, illustrated by real case studies. Monoliths vs Microservices is Missing the Point—Start with Team Cognitive Load Matthew Skelton, Author, Team Topologies: Organizing Business and Technology Teams for Fast Flow Manuel Pais, Author, Team Topologies: Organizing Business and Technology Teams for Fast Flow Matthew Skelton has been building, deploying, and operating commercial software systems since 1998. Head of Consulting at Conflux (confluxdigital.net/), he specialises in Continuous Delivery and operability for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software. Matthew curates the well-known DevOps team topologies patterns at devopstopologies.com and is co-author of the books Continuous Delivery with Windows and .NET (O’Reilly, 2016) and Team Guide to Software Operability (Skelton Thatcher Publications, 2016). He is also co-founder at Skelton Thatcher Publications (skeltonthatcher.com/), a specialist publisher of techniques for software teams. Matthew founded and leads the 2300-member London Continuous Delivery meetup group (londoncd.org.uk/), and instigated the first conference in Europe dedicated to Continuous Delivery, PIPELINE Conference (pipelineconf.info/). He also leads the CodeMill digital skills initiative in the North of England (codemill.tech/), and is a Chartered Engineer (CEng). Manuel Pais is an independent IT consultant and trainer, focused on team interactions, delivery practices, and accelerating flow. Manuel is co-author of the book "Team Topologies: Organizing Business and Technology Teams for Fast Flow" (IT Revolution Press, 2019). He helps organizations rethink their approach to software delivery, operations and support via strategic assessments, practical workshops, and coaching. Also InfoQ lead editor. Answers by @manupaisable on Twitter and Medium. DOES19 London DOES 2019 EUR DevOps Enterprise Summit events.itrevolution.com/eur/

Why it's here

2 people recommend this

What people say. Highly recommended by SREs as a refreshing perspective on optimizing team structures, workflows, and internal platform dynamics.

u/kvgruin r/sre • Recommends

…rised at how religiously people follow their beliefs when it comes to infrastructural choices, team setups, workflow and pipeline designs, etc. Monoliths vs microservices, you build it you run it vs separation of concerns, and all the endless debates. I found Matthew Skelton and Manuel Pais' Team topologies talk really refreshing in this respect [video The focus for any SRE/Ops/Platform team should be to optimize your setup and workflows to reduce cognitive load on developers and eventually enable self-service i.e. REAL you build it you run it. Independently of following your specific setup religion. Manuel Pais in particular focuses on internal platform as the key layer to allow develop…

u/matgaltin r/sre • Recommends

The importance of Internal Platform teams Last year I met Manuel Pais at Kubecon Berlin and we instantly connected on the topic of the book he had published at the time: Team topologies (here's his talk with his co-author when they launched it). Teams are the fundamental building block of organizations, how those teams work and the system they operate in are the difference between average and high performance. In our DevOps universe, we often argue about architectural decisions such as monoliths vs microservices. However, the most effective optimization we can often do is not on the infrastructure level, but rather on the more fundamental team layer. In Manuel's words: we should optimiz…