Silesia JUG #102 - Jakub Nabrdalik - Modules & Microservices - workshop

Modules & Microservices, how to design and think about them, a pragmatic approach

Can you give a definition of a module? Do you know why a good modular design is a shitty microservice design and vice versa? Let me help you clarify this a bit. I'll show you some rules for modular monoliths and microservices which allow me to deliver systems that are easy to maintain, easy to work with, fast and secure (enough). I'll teach you what to look for in both architectures, based on mistakes I see people make over and over again. We will cover: - what are the rules of modularity, how modules and microservices communicate - when to put things into modules of the same app, and when you definitely want to separate - read models, events, how to design a fast distributed system and how to notice a slow design even without performance tests - simple checks to keep your design easy to work with and healthy on production - examples of disasters when we don't do that - and a few more architecture ideas This is a 6h short version of my 3 day long workshop on modular monoliths, microservices and event driven systems. Squeezed down to pure essence, practical stuff only.

Bio

23 years designing and building systems as an architect, developer, manager
15 years speaking at conferences and workshops about microservices, modularity, TDD/BDD, DDD

Partners of the workshop are:
GTC S.A. - providing the space for the meeting

Vattenfall IT Services Poland - supporting us in organization the meeting