Why You Should Never Build Microservices - and Why We Do It Anyway

Why You Should Never Build Microservices - and Why We Do It Anyway

NDC Conferences via YouTube Direct link

Monolith

28 of 36

28 of 36

Monolith

Class Central Classrooms beta

YouTube playlists curated by Class Central.

Classroom Contents

Why You Should Never Build Microservices - and Why We Do It Anyway

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

  1. 1 Introduction
  2. 2 What are Microservices
  3. 3 Why we like Microservices
  4. 4 Layered architecture
  5. 5 Complexity
  6. 6 Promises
  7. 7 Value
  8. 8 People
  9. 9 Smaller teams
  10. 10 Deployment pipelines
  11. 11 Advanced Network layer
  12. 12 Multiple programming languages
  13. 13 Debugging
  14. 14 Multiple Services
  15. 15 Error Cases
  16. 16 Monitoring
  17. 17 Tests Debugging
  18. 18 Unit Tests
  19. 19 Pitfalls
  20. 20 Not enough skilled people
  21. 21 Distributed monolith
  22. 22 Eventually consistency
  23. 23 Crossfunctional teams
  24. 24 Bounded context domains
  25. 25 Availability reliability
  26. 26 Thoughts on Microservices
  27. 27 Perfection
  28. 28 Monolith
  29. 29 Picking out pieces
  30. 30 Look for bounded contexts
  31. 31 Layers
  32. 32 Architecture
  33. 33 Minimum requirements
  34. 34 Development environments
  35. 35 Logging monitoring
  36. 36 Technology

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.