Microservices: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 15: Line 15:


* https://livebook.manning.com/#!/book/microservices-in-net-core/chapter-1/7
* https://livebook.manning.com/#!/book/microservices-in-net-core/chapter-1/7
* Monoliths vs. Microservices https://medium.com/koodoo/house-of-cards-architecture-af88c39b679f
* Monoliths vs. Microservices, a House of Cards analogy https://medium.com/koodoo/house-of-cards-architecture-af88c39b679f


=Overview=
=Overview=

Revision as of 14:19, 29 January 2019

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