Microservices: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 24: Line 24:
* http://basho.com/posts/technical/microservices-please-dont/
* http://basho.com/posts/technical/microservices-please-dont/
* https://content.pivotal.io/blog/should-that-be-a-microservice-keep-these-six-factors-in-mind
* https://content.pivotal.io/blog/should-that-be-a-microservice-keep-these-six-factors-in-mind
* Chris Richardson's https://www.infoq.com/articles/microservices-intro

Revision as of 02:01, 24 August 2018

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.

To Process