1. 1. Server Director @ Gogolook System Dynamics Model of Microservices Adoption
2. 2. http://www.gartner.com/smarterwithgartner/top-10-technology-trends-impacting-infrastructure-operations/
3. 3. http://www.gartner.com/smarterwithgartner/top-10-technology-trends-impacting-infrastructure-operations/
4. 4. Microservices
5. 5. 2015 2016
6. 6. 2016 2017
7. 7. Hardware Communication App platform Microservices Domain-driven design DevOps:Jenkins, GitLab, ELK, Prometheus Service infra:ZooKeeper, etcd, Consul, Kafka Server infra:Ansible, Docker, Kubernetes, Mesos, OpenStack, db Microservice ecosystem: 4-layer model
8. 8. model around business concepts adopt a culture of automation hide internal implementation details decentralize all the things deploy independently isolate failure highly observable Domain-driven design CI/CD: Jenkins, GitLab, Docker ecosystem API-rst design: RAML, Swagger DevOps: Ansible, Docker, Kubernetes Async choreography: ZooKeeper, etcd, Kafka Anti-fragility: Akka, Netix OSS Monitoring: Prometheus, ELK
9. 9. One Piece
10. 10. Microservices
11. 11. System Dynamics Model of Microservices Adoption
12. 12. Accidental Adversaries Shifting the Burden
13. 13. Dev velocity Need for improving architecture Size of a single service instance Stability Actions to increase operations eciency # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Desire to take fundamental solutions # unplanned work Operation complexity Actions to merge services Near- sightedness Accidental Adversaries Shifting the Burden
14. 14. Dev velocity Need for improving architecture Size of a single service instance Stability Actions to increase operations eciency # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Desire to take fundamental solutions # unplanned work Operation complexity Actions to merge services Near- sightedness Lets Begin!
15. 15. Dev velocity Need for improving architecture Size of a single service instance Actions to split services
16. 16. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Operation complexity Actions to merge services Actions to split services
17. 17. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services
18. 18. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services
19. 19. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services
20. 20. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services or
21. 21. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services
22. 22. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Operation complexity Actions to merge services Accidental Adversaries
23. 23. Stability # services Need for proper coordination Operation complexity Actions to merge services
24. 24. Stability # services Need for proper coordination Actions to enhance anti-fragility Operation complexity Actions to merge services model around business concepts adopt a culture of automation hide internal implementation details decentralize all the things deploy independently isolate failure highly observable
25. 25. Stability Actions to enhance anti-fragility Actions to merge services ?Two roads diverged in a wood, and I
26. 26. Stability # services Need for proper coordination Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness
27. 27. Stability Actions to enhance anti-fragility Desire to take fundamental solutions Actions to merge services Near- sightedness
28. 28. Stability # services Need for proper coordination Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness
29. 29. # services Need for proper coordination Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness Stability Actions to enhance anti-fragility
30. 30. # services Need for proper coordination Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness Stability Actions to enhance anti-fragility model around business concepts adopt a culture of automation hide internal implementation details decentralize all the things deploy independently isolate failure highly observable Domain-driven design CI/CD: Jenkins, GitLab, Docker ecosystem API-rst design: RAML, Swagger DevOps: Ansible, Docker, Kubernetes Async choreography: ZooKeeper, etcd, Kafka Anti-fragility: Akka, Netix OSS Monitoring: Prometheus, ELK microsevices
31. 31. Actions to enhance anti-fragility Desire to take fundamental solutions Near- sightedness Stability # services Need for proper coordination Operation complexity Actions to merge services
32. 32. # services Need for proper coordination Operation complexity Stability Actions to enhance anti-fragility Desire to take fundamental solutions Actions to merge services Near- sightedness
33. 33. Stability # services Need for proper coordination Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness
34. 34. Stability # services Need for proper coordination Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness Shifting the Burden
35. 35. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness
36. 36. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness Accidental Adversaries Shifting the Burden
37. 37. Desire to take fundamental solutions Near- sightedness Actions to merge services Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Operation complexity Shifting the Burden
38. 38. Dev velocity Stability Actions to increase operations eciency # unplanned work Accidental Adversaries
39. 39. Desire to take fundamental solutions Near- sightedness Actions to merge services Dev velocity Need for improving architecture Size of a single service instance Stability Actions to increase operations eciency # services Need for proper coordination Actions to split services Actions to enhance anti-fragility # unplanned work Operation complexity
40. 40.
41. 41. One Piece
42. 42. Accidental Adversaries Shifting the Burden
43. 43. Dev velocity Need for improving architecture Size of a single service instance Stability # services Need for proper coordination Actions to split services Actions to enhance anti-fragility Desire to take fundamental solutions Operation complexity Actions to merge services Near- sightedness Accidental Adversaries Shifting the Burden
44. 44.
45. 45. http://DevOpsTW.club