Microservices: A Utopian mystery

Adapted slides from the microservices talk at London Microservices meetup.

https://www.meetup.com/London-Microservices-User-Group/events/225204250/

Transcript

2. MICROSERVICES A UTOPIAN MYSTERY PRAVEENA FERNANDES @praveenasekhar
3. Microservices (µservices) is a software architecture style in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. @praveenasekhar
4. Utopia : An imagined place or state of things in which everything is perfect. Mystery: Something that is difficult or impossible to understand or explain. @praveenasekhar
5. Lesson 1: Keep it small @praveenasekhar
6. Why should my story to improve query performance be blocked because of a UI bug? @praveenasekhar
7. @praveenasekhar
8. Smaller codebase leads to smaller contexts to change leads to autonomous delivery @praveenasekhar
9. Lesson 2: Focus on autonomy, from design to deployment. @praveenasekhar
10. Autonomy: The right or condition of self-government. @praveenasekhar
11. How does autonomy look like? @praveenasekhar
12. Want: No choreographed deployments Need: Easy choreographed deployments @praveenasekhar
13. Make a conscious decision to think about your deployment strategy when you start with a story and slowly you’ll see deployment patterns evolve. @praveenasekhar
14. Lesson 3: Plan for contingency aka breaking changes. @praveenasekhar
15. What about breaking changes?
16. • Semantic Versioning • Tolerant Reader • Lock step deployment • Feature Toggles @praveenasekhar
17. Lesson 4: Pay attention to your bounded context. @praveenasekhar
18. Bounded Context @praveenasekhar
19. { “authToken” : “token123”, “username” : ”John”, “age” : 28 } @praveenasekhar
20. { “authToken” : “token123”, “username” : ”John”, “age” : 28 } { “user” : { “name” : ”John”, “age” : 28 } } @praveenasekhar
21. Lesson 5: Choose what works best for you and document your reasons. @praveenasekhar
22. 2 2 Constraints vs Principles @praveenasekhar
23. 2 3 Ex: It is ok to duplicate validations @praveenasekhar
24. 2 4 Some duplications are better than other duplications. @praveenasekhar
25. 2 5 Shared libraries/shared clients? @praveenasekhar
26. 2 6 Good abstraction: Managing negative ttl caching can be abstracted to a shared library. @praveenasekhar
27. 2 7 Bad abstraction: Abstract models into shared libraries. @praveenasekhar
28. Sharing Customer, Product models is a bad idea. @praveenasekhar
29. Lesson 6: Embrace Conway’s law @praveenasekhar
30. Conway’s law Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. @praveenasekhar
31. Horizontal slicing: UI Team, Platform team, Feature team. Vertical slicing: Feature team with developers, testers, platform, UI developers and product owners. @praveenasekhar
32. @praveenasekhar
33. SCS: Self contained systems Product Owners vs Gatekeepers for change @praveenasekhar
34. Lesson 7: Take monitoring seriously. @praveenasekhar
35. Monitoring @praveenasekhar
36. • Business Metrics • Application Metrics • System Metrics @praveenasekhar
37. • Kibana • Grafana • Graphite • Turbine • Riemann @praveenasekhar
38. Lesson 8: Testing; Do it! @praveenasekhar
39. Practice testing and release in QA @praveenasekhar
40. Marry monitoring and testing @praveenasekhar
41. • Chaos monkey • Health checks to check for dependent services. • System status dashboards. @praveenasekhar
42. Unit Tests Integration Test Functional Test Journey Tests @praveenasekhar
43. Unit Tests Integration Test Functional Test Service Test Contract Tests Journey Test @praveenasekhar
44. Note: Tests are to validate constraints, they shouldn’t be constraints themselves. @praveenasekhar
45. Lesson 9: Invest in infrastructure @praveenasekhar
46. Invest in infrastructure @praveenasekhar
47. @praveenasekhar
48. Lesson 10: Embrace new technology @praveenasekhar
49. Evolving ecosystem
50. Digital Disruption • Uber • Airbnb • Facebook • Netflix • … @praveenasekhar
51. New kids on the block • Containerisation. • Service Registry. • AWS Lambda. • Ephemeral Containers. • *aaS @praveenasekhar
52. Dan Pink’s Drive : https://www.youtube.com/watch?v=u6XAPnuFjJc @praveenasekhar
53. • Improve in iterations • Have autonomy, take control for business as well as technology. • High cohesion and loosely coupled. • Embrace Conway’s law. Don’t fight it. • Have fun. @praveenasekhar
54. Summary Keep it small. Focus on autonomy, from design to deployment. Plan for contingency, aka breaking changes. Pay attention to your bounded context. Choose what works best for you and document your reasons. Embrace Conway’s law. Take monitoring seriously. Testing; Do it. Invest in infrastructure. Embrace new technology. @praveenasekhar
55. Resources @praveenasekhar
56. Thank You ☺