Download as PDF, PPTX
Uploaded bySmartBear
Microservices Architecture: Building 'SMART' & 'Agile' Software
The document discusses microservices architecture, detailing its evolution and key principles essential for developing agile software applications. It emphasizes the benefits of microservices, such as technology heterogeneity, ease of deployment, organizational alignment, and resilience among services. Additionally, the document outlines principles for effective microservice design and the importance of investing in team alignment and infrastructure automation for successful implementation.
Microservices Architecture: Building 'SMART' & 'Agile' Software
- 1. Microservices Architecture Building 'SMART'& 'Agile' Software Sabby Gupta {Product Architect -> Zaloni Inc.} 1
- 2. What’s in itfor me? 2
- 3.
- 4. History 2010s2000s1990s1980s< 1970s Netflix, Amazon, Googlemanage their growth - apis, devops, distributed paradigm SOA, Mobile, Efficiency & Cost savings, Agile, CI/CD LISP, PROLOG, ERLANG, SMALLTALK Web Services - Microsoft lead, DCOM/CORBA Actor Model (Carl Hewitt) and human services (do one thing right) 4
- 5.
- 6. Microservice architectural styleis an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. ~Martin Fowler~ 6
- 7. Compare to SOA? ●Horizontal vs Vertical Design ● Reusability ● Governance Standards ○ Web Services (WS-*), XML, HTTP, SOAP etc ● EAI - ESB Focus - Smart Pipes ● Popularity of containers ● SOA DONE RIGHT (opinionated way)!! 7
- 8.
- 9.
- 10.
- 11.
- 12. Resilience Bulkheading - managefailure without having it cascade throughout the services participating in the workflow 12
- 13.
- 14.
- 15.
- 16. Organizational Alignment “Any organizationthat designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization’s communication structure.” ~Melvin Conway~ If you have four groups working on a compiler, you’ll get a 4-pass compiler. ~Eric S. Raymond~ 16
- 17.
- 18. Development & OpsProcess 18
- 19.
- 20.
- 21. Principle 1 -Business Domain Modelling & Responsibilities Order Customer Bonus Program # Delivery Customer Delivery Address Delivery Service Type Billing Customer Billing Address Tax Rate 21
- 22.
- 23. Principle 2 -Automation 23
- 24. Principle 3 -Encapsulate & Aggregate 24
- 25. Principle 4 -Autonomy / Self-Service 25
- 26. Dumb Pipes, SmartEndpoints 26
- 27. Principle 5 -Deploy Independently Service :: Host Consumer Driven Contracts Versioning 27
- 28. Principle 6 -Api First Design Documentation 28
- 29. Principle 6 -Api First Design Service Discovery 29
- 30. Principle 7 -Failure Isolation Bulkheading Circuit Breaker 30
- 31. Principle 8 -Devops Log Aggregation Stats Aggregation Service Ops Correlation 31
- 32. Principle 9 - Organizational Culture& Psychological Safety ~Peter Drucker~ 32
- 33. Silver Bullet? - Investin aligning teams to service architecture - Invest in understanding and modeling business domain - Invest in infra automation - Invest in automated testing - Invest in Continuous Delivery - Invest in API First Design - Will experience hockey stick growth in microservice adoption - OK to start monolithic and move to microservices 33
- 34. Thanks! Contact us: Zaloni Inc 633Davis Dr, Durham, NC 27709 sgupta@zaloni.com @sabygupta https://www.linkedin.com/in /sabyasachigupta/ 34