Microservices - why's and how's
Download as PPTX, PDF1 like191 views
The document discusses the differences between layered architecture and hexagonal architecture (microservices). It highlights how a monolithic layered architecture complicates scaling and maintenance, while a hexagonal architecture supports loose coupling and seamless scaling of independent components. Additionally, it covers various components of microservices such as ports, adapters, and the role of service brokers in an agile development environment.
Microservices - why's and how's
- 1. Introduction to Microservices – A peek into Hexagonal Architecture vs. a layered one UI / Presentation Application Integration Persistence / Mock DB DB Test Agent A layered architecture: Architectural components stacked up and communicating over interfaces to form a monolith. Actual implementation details (threads, contexts) tend to leak across layers and make the architecture harder to scale and maintain for the inherent complexities. A hexagonal (Microservice) architecture: Loosely coupled contexts and independent architectural components communicating via ports, adapters and binding based dependencies only. Applications can be seamlessly scaled without bounds. Maintenances are simple and customizable to the NFR / business asks of each components. Application Port Adapter Adapter Port Port UI / Presentation Adapter Test Agent Integration Port Adapter Persistence / Mock DB DB Use case boundary
- 2. Anatomy of a typical microservice, architecture and development environment Application Application logs PortAdapter Adapter Security provider Network / Infrastructure Adapter Application config Environment config Port Auth Services Port Logging tools Security token Subscriptions Adapter Network configs Port The API accelerators AdapterPort Adapter Legend Configurations Accelerators - Code / API/ Frameworks / Scaffolding generation Development efforts Proprietary / 3rd Party Systems API Proxy / Gateway Adapter Adapter Sidecar Kubernetes Pods SERVICE BROKER Agile Feature / Component Teams Feature team 1 Feature team 2 Component team Adapter Marketplace Services Service registry DB services Log analytics services API metrics services Big Data adapters Autoscaling services Message queue services Cloud Broker Services Kubernetes Pods Mesh of Microservice aggregates Sidecar