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 - What I've learned after a year building systems

277 views

Published on

This presentation covers what I've learned about using microserivices over the last year, the things you want to be doing and problems you can run into.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Microservices - What I've learned after a year building systems

  1. 1. Microservices WHAT I’VE LEARNED AFTER A YEAR BUILDING SYSTEMS www.designcoderelease.blogspot.com@NathanGloyn
  2. 2. @NathanGloyn www.designcoderelease.blogspot.com Disclaimer
  3. 3. @NathanGloyn www.designcoderelease.blogspot.com Agenda Why use microservices? Aspects of microservices Development Testing Data Deployment The reality of a live system
  4. 4. @NathanGloyn www.designcoderelease.blogspot.com Why use microservices?
  5. 5. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Different way of thinking
  6. 6. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Different way of thinking
  7. 7. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Different way of thinking
  8. 8. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Different way of thinking
  9. 9. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Identifying services
  10. 10. @NathanGloyn www.designcoderelease.blogspot.com Aspects – messaging
  11. 11. @NathanGloyn www.designcoderelease.blogspot.com Aspects – messaging MessageBus
  12. 12. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Fat vs Thin Vs
  13. 13. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Distributed system
  14. 14. @NathanGloyn www.designcoderelease.blogspot.com Aspects – Security
  15. 15. @NathanGloyn www.designcoderelease.blogspot.com Development – repositories or
  16. 16. @NathanGloyn www.designcoderelease.blogspot.com Development – Technology Stack
  17. 17. @NathanGloyn www.designcoderelease.blogspot.com Development – shared functionality
  18. 18. @NathanGloyn www.designcoderelease.blogspot.com Development - UI
  19. 19. @NathanGloyn www.designcoderelease.blogspot.com Testing
  20. 20. @NathanGloyn www.designcoderelease.blogspot.com Deployment
  21. 21. @NathanGloyn www.designcoderelease.blogspot.com Live system – Configuration
  22. 22. @NathanGloyn www.designcoderelease.blogspot.com Live system – Data
  23. 23. @NathanGloyn www.designcoderelease.blogspot.com Live system – Logging
  24. 24. @NathanGloyn www.designcoderelease.blogspot.com Live system – Monitoring
  25. 25. @NathanGloyn www.designcoderelease.blogspot.com Live system – Custom tools
  26. 26. @NathanGloyn www.designcoderelease.blogspot.com Summary Different way of thinking Choice of technology not necessarily important but at same time can be crucial Service identification is important and if should be fat or thin dependent upon resilience Put configuration in one place You will need to alter data in production – know how you are going to do this Log, log and log some more Monitor the system not just individual services
  27. 27. Questions? www.designcoderelease.blogspot.com@NathanGloyn

×