Skip to content

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

  1. 0:00 Intro
  2. 0:34 How does this happen
  3. 1:09 Great architecture
  4. 1:55 Notsogreat architecture
  5. 2:29 How to avoid spaghetti
  6. 2:44 My background
  7. 3:37 Misconceptions
  8. 4:31 Cogeneration is evil
  9. 4:54 Event log must be the source
  10. 5:47 Developers can maintain no more than 3 services
  11. 6:05 The wrong metric to focus on
  12. 6:35 Flow Architecture
  13. 10:20 Breaking Changes
  14. 10:49 API Builder
  15. 11:49 Code Generation
  16. 12:58 Routes
  17. 14:09 Client Libraries
  18. 15:30 Mock Clients
  19. 16:39 Writing Code
  20. 17:24 Database Architecture
  21. 22:54 Testing
  22. 24:16 Time to Deploy
  23. 24:23 Continuous Delivery
  24. 26:37 Delta
  25. 27:04 Configuration
  26. 27:45 Health Checks
  27. 28:45 Events
  28. 28:49 API
  29. 29:34 Event Interface
  30. 31:38 Producer Interface
  31. 32:41 Consumer Interface
  32. 36:12 Journaling
  33. 37:57 Stream
  34. 38:55 Product Testing
  35. 39:35 Consumer Testing
  36. 40:34 Dependencies
  37. 41:59 Floaty IO
  38. 43:03 Upgrade SC
  39. 44:00 Summary
  40. 46:47 Questions
Channel
InfoQ
Views
233

More like this