微服務導入趨勢 (System Dynamics Model of Microservices Adoption)

1. 微服務導入趨勢 Server Director @ Gogolook 葉秉哲　 System Dynamics Model of Microservices Adoption

2. http://www.gartner.com/smarterwithgartner/top-10-technology-trends-impacting-infrastructure-operations/

3. http://www.gartner.com/smarterwithgartner/top-10-technology-trends-impacting-infrastructure-operations/

4. 結論／ Microservices 很夯！

5. 2015 2016

6. 2016 2017

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. 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, Netﬂix OSS… Monitoring: Prometheus, ELK…

9. ⼤大秘寶  One Piece

10. 疑點／很多⼈人嘗試導入 Microservices，卻失敗了了？

11. 我的切入點／ System Dynamics Model of Microservices Adoption

12. 意外的敵⼈人 Accidental Adversaries 捨本逐末 Shifting the Burden

13. Dev velocity Need for improving architecture Size of a single service instance Stability Actions to increase operations eﬃciency # 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. Dev velocity Need for improving architecture Size of a single service instance Stability Actions to increase operations eﬃciency # 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 Let’s Begin!

15. Dev velocity Need for improving architecture Size of a single service instance Actions to split services 平衡迴路路；穩定均衡態

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. 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. 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. 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 負增強

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. Stability # services Need for proper coordination Operation complexity Actions to merge services

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. 林林⼦子裡有兩兩條分歧的路路，⽽而我⋯⋯ Stability Actions to enhance anti-fragility Actions to merge services ?Two roads diverged in a wood, and I…

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. Stability Actions to enhance anti-fragility Desire to take fundamental solutions Actions to merge services Near- sightedness

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. # 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. # 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, Netﬂix OSS… Monitoring: Prometheus, ELK… 撇開 microsevices 不論，試問：這些是本來來就該做的嗎？本？

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. # 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. 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. 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. 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. 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. 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. Dev velocity Stability Actions to increase operations eﬃciency # unplanned work 意外的敵⼈人 Accidental Adversaries

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 eﬃciency # services Need for proper coordination Actions to split services Actions to enhance anti-fragility # unplanned work Operation complexity

40. 總結

41. ⼤大秘寶  One Piece

42. 意外的敵⼈人 Accidental Adversaries 捨本逐末 Shifting the Burden 嘗試導入前，請先做些系統思考

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. 知道何時該堅持，何時該妥協，以及為何妥協。

45. http://DevOpsTW.club

微服務導入趨勢 (System Dynamics Model of Microservices Adoption)

You are reading a preview.

微服務導入趨勢 (System Dynamics Model of Microservices Adoption)

More Related Content

More from William Yeh

Featured

Related Books

Related Audiobooks