Microservice
Download as PPTX, PDF•0 likes•249 views
This document discusses microservices, an architectural approach where a single application is composed of small, independent services that communicate with each other. Microservices allow for independent development and deployment of each service by different teams using various programming languages and tools. However, microservices also introduce operational overhead, require substantial DevOps skills, and make testing and asynchronous communication more challenging.
Microservice
- 1. Microservices Want to learn more: http://martinfowler.com/articles/microservices.html WHY Microservices? • Each Microservice is quite simple being focused on one business capability • Microservices can be developed independently by different teams • Microservices are loosely coupled • Microservices can be developed using different programming languages and tools WHY NOT Microservices? • Significant Operation Overhead • Substantial DevOps Skills Required • Implicit Interfaces • Duplication Of Effort • Distributed System Complexity • Asynchronicity Is Difficult! • Testability Challenges Microservice Communications WHAT is Microservice? Microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweightmechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery.