What I Learned Building a Microservices Architecture
summary
Covers building microservices architectures: the talk explains why to use microservices, how architectures are assembled, and which technologies are used (including containers and FaaS). It also describes how these architectures are tied to agile practices such as testing, continuous integration and continuous delivery, with examples from .NET, Node.js and Docker adoption.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:50Microservices risks for companies
- 3:39Microservices architecture principles
- 8:59Service size and definition
- 10:45Common infrastructure and utilities
- 12:56Databases and independence
- 14:00Public cloud and monitoring
- 15:23AWS Lambda limitations
- 17:31Azure Apps Service vs containers
- 18:35Why choose containers
- 21:27Cloud portability and lock-in
- 22:30Kubernetes benefits
- 23:13Service independence
- 25:40Service versioning
- 28:11Legacy system integration
- 29:16Communication protocols
- 30:43Timeouts and circuit breakers
- 32:30Log correlation and traceability
- 33:13Eventual consistency and sagas
- 34:16Queues and messaging
- 34:38DevOps and per-service repos
- 35:42End-to-end tests and environment
- 36:46Secrets and configuration management
- 38:09Technologies and performance
- 39:12Summary and final recommendations
related talks
59mWhat We Learned Building Microservices
39mImplementing Microservices: How and Why
32mMicroservices: A retrospective
49mMicroservices: An unexpected Journey
56mMicroservice Architecture
54mMicroservice architecture: approaches and technologies
38mIntroduction to Microservices
52mI Have a Microservices Architecture and I Didn't Know.