Microservices: Difference between revisions
| Line 19: | Line 19: | ||
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. | 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= | =To Process= | ||
Revision as of 19:39, 10 November 2018
Internal
External
- Martin Fowler's Microservices Resource Guide http://martinfowler.com/microservices/ https://martinfowler.com/articles/microservices.html
- Adrian Cockcroft on Microservices, Terraservices and Serverless Computing https://www.infoq.com/articles/podcast-adrian-cockcroft
- https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/microservice_architecture/
- Anil's:
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
- http://basho.com/posts/technical/microservices-please-dont/
- 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
- The Hidden Dividends of Microservices https://queue.acm.org/detail.cfm?id=2956643