London Microservices Meetup [Online]

Agenda:

6:30 pm: Brief introductions

6:35 pm: Monoliths vs Microservices is the Wrong Question - Start with Team Cognitive Load by Manuel Pais

7:15 pm: Quick 5-minute break

7:20 pm: Microservices: A Taxonomy by Stefan Tilkov (INNOQ)

8:00 pm: Finish

----

We're big supporters of Teck Camp: https://teck.camp. If you would like to attend this event but you feel overwhelmed by the idea of going and networking by yourself, Teck Camp is a great way to connect with like-minded people to go to events with!

----

Monoliths vs Microservices is the Wrong Question - Start with Team Cognitive Load
Manuel Pais

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 I explain how and why.

Key takeaways:

• What is team cognitive load and why that matters
• Using team cognitive load as the guiding principle for sustainable ownership and evolution of software systems
• What are the fundamental topologies and interaction modes that help reduce cognitive load

Manuel Pais is co-author of "Team Topologies: organizing business and technology teams for fast flow". Recognized by TechBeacon as a DevOps thought leader, Manuel is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices and accelerating flow. Manuel is also a LinkedIn instructor on Accelerating Continuous Delivery in the Enterprise.

----

Microservices: A Taxonomy
Stefan Tilkov, INNOQ

A microservices services architecture has become a standard way to approach the modular design of large scale systems. But while there are some traits that most practitioners can agree on, such as independent deployment, choice in implementation details, polyglot persistence, and benefits such as isolation, better parallelization, and improved scalability, there are still vast differences between the diverse approaches taken in practice. In this talk, we will categorize different ways to approach the architectural style, and highlight differences, benefits, and downsides of various interpretations found in projects.

Key takeaways:

• Size is the distinguishing factor of most microservices approaches
• Different goals create completely different incentives for which approach is the best
• Size influences major architectural decisions, such as the usefulness of micro-frontends

Stefan is a founder and principal consultant at INNOQ, where he spends his time alternating between advising customers on new technologies and taking the blame from his co-workers for doing so. He is a frequent speaker at conferences and author of numerous articles.