Preparing For a Future Microservices Journey Using Wardley Maps -

on YouTube ↗50m

" summary

Claims microservices market reaches 33 billion by 2023 and adoption hits late majority while loose coupling still lags; uses Wardley Maps plus Domain-Driven Design to map components to evolution stages and decide build vs buy. Concrete stack examples: Elasticsearch, MongoDB, Docker, Kubernetes, Istio, Keycloak, Vault, Netflix OSS, Spring Cloud, Prometheus/Grafana and a runnable example that wires AWS Lambda + DynamoDB + SNS for a CFP flow, showing tradeoffs: orchestration/service mesh reduce ops work but add new primitives, serverless shifts infra to utilities.

AI-written summary · about

" chapters (7)

1. 0:00Introduction to microservices journey
2. 5:50Wardley Maps overview
3. 15:32Domain-driven design with maps
4. 23:47Core vs supporting subdomains
5. 31:58Evolving infrastructure complexity
6. 41:01Serverless and cloud services
7. 47:24Key takeaways and summary

" related talks

• 45mWardley Maps for Your Microservices JourneySusanne Kaiser · Build Stuff 2019
• 44mArchitecture for Flow - Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · DDD Europe 2022
• 49mMicroservices: An unexpected JourneySam Newman · JavaDay Ukraine 2017
• 01h 18mIn Defense of MicroservicesChad Green · Conf42 Cloud Native 2025
• 24mPatterns of Evolution from Monolith to MicroservicesKarina Mora · HashiTalks 2022
• 24mDistant Past of MicroservicesKen Finnigan · Voxxed Days Microservices 2018
• 31mPast, Present and Future of MicroservicesSebastien Stormacq · Voxxed Days Microservices 2019
• 50mX Marks the Spot: Navigating Possible Futures with Wardley MapsSimon Wardley · GOTO Amsterdam 2024