Microservices: Difference between revisions
No edit summary |
No edit summary |
||
(15 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=Internal= | |||
* [[Software Development#Microservices|Software Development]] | |||
* [[Serverless Computing]] | |||
=External= | =External= | ||
* Martin Fowler's Microservices Resource Guide http://martinfowler.com/microservices/ | * 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 | * 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: | |||
** https://hackernoon.com/development-of-microservices-problems-and-solutions-b3ce8f1f7ff1#.h88lojeqh | ** https://hackernoon.com/development-of-microservices-problems-and-solutions-b3ce8f1f7ff1#.h88lojeqh | ||
** https://medium.com/@anil789/micro-applications-and-decomposition-of-ui-1062e3b1a345#.b3rid28v8 | ** https://medium.com/@anil789/micro-applications-and-decomposition-of-ui-1062e3b1a345#.b3rid28v8 | ||
Line 9: | 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, a House of Cards analogy https://medium.com/koodoo/house-of-cards-architecture-af88c39b679f | |||
=Overview= | =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. | 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 | |||
* 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 |
Revision as of 14:19, 29 January 2019
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:
- https://livebook.manning.com/#!/book/microservices-in-net-core/chapter-1/7
- Monoliths vs. Microservices, a House of Cards analogy https://medium.com/koodoo/house-of-cards-architecture-af88c39b679f
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
- 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