Tips for Failing at Microservices

Tips for Failing at Microservices

Devoxx via YouTube Direct link

A system stable as concrete sounds good

16 of 35

16 of 35

A system stable as concrete sounds good

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Tips for Failing at Microservices

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Disclaimer
  3. 3 Go full scale polyglot
  4. 4 Still successful?
  5. 5 Polyglot?
  6. 6 The data monolith
  7. 7 The event monolith
  8. 8 How to deal with shared code?
  9. 9 2 months later...again
  10. 10 The home grown monolith
  11. 11 And at runtime???
  12. 12 The meat cloud
  13. 13 And the rest of the world?
  14. 14 Tickets!
  15. 15 a few minutes later
  16. 16 A system stable as concrete sounds good
  17. 17 The decision monolith
  18. 18 Beware developer madness
  19. 19 Change management
  20. 20 Bonus: works with ops, too
  21. 21 The prescriptive cloud
  22. 22 One Size Fits All
  23. 23 PolyWTF works for ops
  24. 24 The staffing monolith
  25. 25 Frequent Flyer Program Rail-Bonus Program Hotel Credit Points
  26. 26 Dysfunctional setup in 3 easy steps
  27. 27 How to do X-team communication?
  28. 28 Protect the teams
  29. 29 Establish bureaucracy
  30. 30 Enter the fakeholder!
  31. 31 shadow product owner proxy product owner
  32. 32 Technical benefits?
  33. 33 Shared release
  34. 34 And: In case of bugs...
  35. 35 The monolith starts in the head

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.