Microservices: Difference between revisions
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
* 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 | ||
* http://basho.com/posts/technical/microservices-please-dont/ |
Revision as of 17:57, 29 January 2018
Internal
External
- Martin Fowler's Microservices Resource Guide http://martinfowler.com/microservices/
- 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.