Moving to Microservices
Download as PPTX, PDF1 like142 views
The document discusses moving to a microservices architecture. It defines microservices as small, autonomous services that work together and are modeled around business domains. The principles of microservices include automating processes, prioritizing consumers, hiding implementation details, decentralizing systems, deploying independently, and isolating failures. The document outlines challenges in developing microservices and splitting existing monolithic applications into microservices.
Moving to Microservices
- 1. MOVING TO MICROSERVICES Ivan Paulovich github.com/ivanpaulovich ivan@paulovich.net S2IT - May 2018 Hangout
- 2. MICROSERVICES DEFINITION Small Autonomous services that work together, modelled around a business domain. Sam Newman, 2015, Building Microservices
- 3. THE PRINCIPLES Culture of Automation Consumer First Hide Implementation Details Decentralise all the things Deploy Independently Isolate Failure Highly Obervable Modelled Around Business Domain Sam Newman, 2015, Building Microservices Principles of Microservices
- 5. THE BENEFITS • More choices • Requires guided change
- 6. ARCHITECTURE Hexagonal Architecture Layered Application
- 7. MICROSERVICE’S SIZE The physical bounded context in microservices correlates exactly to our concept of architectural quantum — it is a physically decoupled deployable component with high functional cohesion. Evolutionary Architecture, 2017
- 10. FITNESS FUNCTIONS • Low response time • Mobile responsive • Availability • Strong audity trail • Heavy legal compliance • Monitoring • Large # of users An evolutionary architecture supports incremental, guided change as first principle along multiple dimensions. Evolutionary Architecture - 2017
- 11. THE HARD PARTS • Every new microservice could be hard to develop from scratch • Network failures, latency, multiple versions • Technology stack Governance
- 12. GUIDED CHOICES • The perfect examples with – Monitoring – Logging – Security – Correlation IDs – Other capabilities • Service templates for different sizes