Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Microservices

752 views

Published on

From TechRadar

Published in: Technology
  • Be the first to comment

Microservices

  1. 1. MICROSERVICES Rouan Wilsenach @rouanw H o w t o b e g i n u s i n g
  2. 2. 2 “I love those little things!” Anonymous microservices fan
  3. 3. WHAT ?
  4. 4. 4 What it’s not: The monolith
  5. 5. 5 “Microservices are small, autonomous services that work together.” Sam Newman
  6. 6. WHY ?
  7. 7. 7 Do one thing well
  8. 8. 8 The right tool for the job
  9. 9. 9 Easier to replace “Let's face it, all we are doing is writing tomorrow's legacy software” Martin Fowler http://martinfowler.com/bliki/StranglerApplication.html
  10. 10. 10 Less risky to try new technologies
  11. 11. 11 Easier to introduce new practices
  12. 12. 12 Resilience
  13. 13. 13 Independent scaling
  14. 14. 14 Less baggage, more trips
  15. 15. 15 Composability
  16. 16. 16 Four things that get harder with size Change Learning Architecture Deployment
  17. 17. MICROSERVICES ! AND BANKING
  18. 18. 1818 Very transactional business Composing core capabilities Mainframe programs Pace of change
  19. 19. HOW TO START?
  20. 20. 20 Start with one
  21. 21. 21 Know your limits http://martinfowler.com/bliki/MicroservicePrerequisites.html Rapid provisioning Basic Monitoring Rapid application deployment
  22. 22. 22 Smaller is better than big
  23. 23. 23 Start simple
  24. 24. 24 Align each service with customer value
  25. 25. 25 Lightweight frameworks
  26. 26. 26 Write a well-tested, easy to use API
  27. 27. 27 Decoupled collaboration “be conservative in what you do, be liberal in what you accept from others” Postel’s Law http://martinfowler.com/bliki/TolerantReader.html
  28. 28. 28 Working software is the best contract
  29. 29. 29 Simple systems Refactoring between services Tricky things… Identifying boundaries Co-ordinating between teams
  30. 30. ENABLING MICROSERVICES
  31. 31. 31 “organizations which design systems are constrained to produce designs which are copies of the communication structures of these organisations” Conway’s Law
  32. 32. 32 Cultural and organisational shifts
  33. 33. 33 Enable. Don’t prescribe.
  34. 34. 34 Make deployment easy
  35. 35. 35 Monitoring
  36. 36. 36 Versioning
  37. 37. Q & A
  38. 38. @samnewman
  39. 39. SOME PLACES TO START Video •http://www.thoughtworks.com/insights/blog/microservices-nutshell (watch James Lewis’s video near the bottom of the page) Article •http://martinfowler.com/articles/microservices.html (keep an eye on Martin’s blog for more content on Microservices) Book •http://samnewman.io/books/building_microservices/ (Sam’s blog is also great to keep an eye on) ! 39
  40. 40. MICROSERVICES Rouan Wilsenach @rouanw H o w t o b e g i n u s i n g

×