Real-Life Lessons in Microservices with CTO Sander Hoogendoorn@ How to Web Conference

In this talk, Sander Hoogendoorn (former CTO, iBOOD.com) shared how his team transitioned from legacy systems to clean microservices — and all the architectural decisions, patterns, and trade-offs along the way.

With real code examples and lessons from the trenches, this session is packed with insights for anyone building modern, scalable systems — microservices or not.

Over 3,000 attendees from 840 companies, 650 startups, 200 investment funds, and more gathered at How to Web Conference 2024 to connect and discuss the future of technology and business in this region and beyond.

Catch a glimpse of the event in the full after movie: • How to Web Conference 2024 Aftermovie


Website: https://www.howtoweb.co/
LinkedIn:   / howtoweb  
Facebook:   / howtoweb  
Instagram:   / how_to_web  
Twitter: https://x.com/how_to_web

Subscribe to our channel here ►►    / @howtowebconf  

Chapters:

0:20 – What are microservices and why are they controversial?
1:40 – When microservices make sense
5:20 – Case study: Insurance company with COBOL code
7:30 – 6 failed migrations and how microservices helped
8:20 – Case study: E-commerce company & technical debt
9:40 – How dependencies will eventually kill you
10:40 – Architecture style: adaptability over complexity
12:00 – Choosing a unified stack for a small team
13:00 – The internal structure of a microservice
14:30 – Reusable and recognizable architectural patterns
18:00 – Domain complexity: cohesion vs. coupling
19:40 – Unix philosophy & single responsibility principle
20:50 – Domain-Driven Design: Bounded Context explained
22:00 – Example: Same data, different meanings = bad modeling
23:20 – Aggregate pattern & how it fits microservices
26:30 – Why quarterly releases are a bottleneck
27:40 – Real-time feedback as a competitive advantage
29:00 – Automate everything: from code to deployment
30:30 – Test automation: unit, integration, E2E, production
32:00 – The ideal test pyramid
33:30 – Trunk-based development vs. pull requests
35:30 – Who owns the data in a microservices world?
37:30 – Advantages of isolated data storage per service
38:30 – How microservices reshape team collaboration
40:00 – Autonomy, trust, and simplification
41:30 – What we don’t do anymore: Scrum, sprints, ceremonies
42:40 – Micro-teams: solving one problem at a time
43:30 – Final thoughts: use microservices only if needed