Design Microservice Architectures the Right Way
2018
48 min
InfoQ
en
YouTube
Download the slides & audio at InfoQ: https://bit.ly/2ypNF04 Michael Bryzek highlights specific key decisions that very directly impact the quality and maintainability of a microservice architecture, covering infrastructure, continuous deployment, communication, event streaming, language choice and more, all to ensure that teams and systems remain productive and scale. This presentation was recorded at QCon London 2018: https://bit.ly/2hxsoN1 Interested in Software Architecture? Follow the topic on InfoQ: https://bit.ly/2NmIOpa #Microservices #ContinuousDeployment # ContinuousDelivery #InfoQ #QCon #QConNewYork
Chapters
- 0:00 Intro
- 0:34 How does this happen
- 1:09 Great architecture
- 1:55 Notsogreat architecture
- 2:29 How to avoid spaghetti
- 2:44 My background
- 3:37 Misconceptions
- 4:31 Cogeneration is evil
- 4:54 Event log must be the source
- 5:47 Developers can maintain no more than 3 services
- 6:05 The wrong metric to focus on
- 6:35 Flow Architecture
- 10:20 Breaking Changes
- 10:49 API Builder
- 11:49 Code Generation
- 12:58 Routes
- 14:09 Client Libraries
- 15:30 Mock Clients
- 16:39 Writing Code
- 17:24 Database Architecture
- 22:54 Testing
- 24:16 Time to Deploy
- 24:23 Continuous Delivery
- 26:37 Delta
- 27:04 Configuration
- 27:45 Health Checks
- 28:45 Events
- 28:49 API
- 29:34 Event Interface
- 31:38 Producer Interface
- 32:41 Consumer Interface
- 36:12 Journaling
- 37:57 Stream
- 38:55 Product Testing
- 39:35 Consumer Testing
- 40:34 Dependencies
- 41:59 Floaty IO
- 43:03 Upgrade SC
- 44:00 Summary
- 46:47 Questions
- Channel
- InfoQ
- Views
- 233