Pivotal-于澎-從雲原生到事件驅動的微服務設計.pdf

What ? Why ? How? What We See • Complex monolithic systems built over many years as a web of interdependent parts • Poor developer experience and productivity • Slow feature delivery and more bugs • Tactical treatment of symptoms (ex. latency) and not core problems (ex. design) • Technology-focused “horizontal” strategies What We See • Old Application Logic - Poor Documentation • COBOL, PL/I, Assembler, JCL, Easytreve, IDMS, DB2, and the list goes on ... • Tightly Coupled and Brittle Architecture • Expensive Licensing and Maintenance • Rehosting and Batch Offload Approaches • Genuine Desire to Modernize … But How?! We Apply Systems Thinking ● Taking a holistic view to identify and treat root cause System thinking is a problems, not just the painful symptoms method of critical ● It requires a shift of perspective, from ○ Parts to Whole thinking by which one ○ Objects to Relationship can analyze the ○ Structures to Process ● We use agile methods, set measured objectives, relationship between experiment, learn and adapt approaches the system’s parts to ● Systems Thinking requires System Modeling