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.

Observable microservices - Lead Developer NY 2017

359 views

Published on

Slides for the talk I delivered at Lead Developer NY 2017.

Think of this talk as a Microservices 201. You know the basic of microservices and their pros and cons, but can you successfully maintain them in production? Microservices can make your code cleaner and more decoupled but they can be a pain to maintain in production: services writing logs in different places, requests that need to be tracked through multiple endpoints, circuit breakers going off… In this talk, I review these and other operational concerns and I explain how making your microservices “observable” will help you maintain a healthy production environment without driving you crazy.

Published in: Software
  • Be the first to comment

Observable microservices - Lead Developer NY 2017

  1. 1. OBSERVABLE MICROSERVICES Maria Gomez @mariascandella LEAD DEVELOPER NY 2017
  2. 2. Production is a hostile environment!
  3. 3. DISCOVERY
  4. 4. 10.4.5.1:8080
  5. 5. 10.4.5.1:8080 10.4.5.50:8452 10.4.5.25:8457
  6. 6. 10.4.5.1:8080 10.4.5.50:8452 10.4.5.25:8457
  7. 7. 10.4.5.1:8080 10.4.5.50:8452 10.4.5.25:8457 Service Registry Register Router Query SERVER SIDE DISCOVERY
  8. 8. 10.4.5.1:8080 10.4.5.50:8452 10.4.5.25:8457 Service Registry Register Query CLIENT SIDE DISCOVERY
  9. 9. SERVICE DISCOVERY Service Registry DNS Static file
  10. 10. MONITOR
  11. 11. LOGS
  12. 12. LOGS
  13. 13. LOG AGGREGATION
  14. 14. METRICS
  15. 15. METRICS
  16. 16. HEALTH CHECK ENDPOINTS
  17. 17. SYNTHETIC MONITORING https://martinfowler.com/bliki/SyntheticMonitoring.html
  18. 18. SYNTHETIC MONITORING https://martinfowler.com/bliki/SyntheticMonitoring.html Staging
  19. 19. SYNTHETIC MONITORING https://martinfowler.com/bliki/SyntheticMonitoring.html Production
  20. 20. SMART ALERTS
  21. 21. DEBUGGING
  22. 22. CORRELATION IDS Service A Service B Service C Service D Initial Request
  23. 23. CORRELATION IDS Service A Service B Service C Service D Initial Request Correlation Id: 1234 Correlation Id: 1234 Correlation Id: 1234
  24. 24. Discovery Monitoring Debugging
  25. 25. @mariascandella mgomez@thoughtworks.com THANKS!

×