Microservices: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 31: Line 31:
* https://opensource.com/article/18/11/revisiting-unix-philosophy-2018
* https://opensource.com/article/18/11/revisiting-unix-philosophy-2018
* Pre-processed, good talk: Design Microservice Architectures the Right Way Michael Bryzek  CTO of Flow Commerce https://www.infoq.com/presentations/microservices-arch-infrastructure-cd
* Pre-processed, good talk: Design Microservice Architectures the Right Way Michael Bryzek  CTO of Flow Commerce https://www.infoq.com/presentations/microservices-arch-infrastructure-cd
* [[Cohesion|High cohesion]]

Revision as of 21:37, 23 December 2020

Internal

External

Overview

An application based on micro services is composed of small, mostly autonomous components, that are built to offer a specific functionality. A cloud-native application is composed of multiple microservices that communicated through shared infrastructure, in most cases over HTTP/REST. The microservices architecture provides two major advantages: various components can be developed, deployed, monitored, and troubleshot independently, on a service-by-service basis, rather than dealing with the entire application. The second advantage is that a specific layer can be scaled independently by other layers.

James Lewis and Martin Fowler definition: 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 lightweight mechanisms, often an HTTP resource API.

To Process