http://gengwg.blogspot.com/In computing, microservices is a software architecture style, in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs.[1] These services are small, highly decoupled and focus on doing a small task.[2]
Contents [hide]
1 Details
2 History
3 Philosophy
4 Criticism
5 Languages
6 Users
7 Implementations
8 See also
9 References
Details[edit]
Properties of the Microservices architecture:
The services are easy to replace
Services are organized around capabilities, e.g. user interface frontend, recommendation, logistics, billing, etc.
A microservices-based architecture
lends itself to a continuous delivery software development process.
is distinct from a Service-oriented architecture (SOA) in that the latter aims at integrating various (business) applications whereas several microservices belong to one application only
History[edit]
Wiki letter w.svg This section is empty. You can help by adding to it. (September 2014)
Philosophy[edit]
Philosophy of Microservices architecture:
The services are small - fine-grained as a singular business purpose similar to the Unix philosophy of "Do one thing and do it well"
The organization culture should embrace automation of deployment and testing. This eases the burden on management and operations
The culture and design principles should embrace failure and faults, similar to anti-fragile systems.
The services are elastic, resilient, composable, minimal, and complete.
[3] [4] [5]
Criticism[edit]
The microservices architecture is subject to criticism for a number of issues:
services form information barriers[6]
the architecture introduces additional complexity and new problems to deal with, such as network latency, message formats, load balancing and fault tolerance,[7] ignoring one of these belongs to the "Fallacies of Distributed Computing"
testing and deployment are more complicated[7]
the complexity of a monolithic application is only shifted into the network, but persists:
You can move it about but it's still there!
—Robert Annett: Where is the complexity?[8]
Languages[edit]
Jolie [9]
Vertx [10]
Users[edit]
Known users of the Microservices architecture:
Apprenda[11]
Cloud Foundry[7]
HP Helion Development Platform
Bluemix
AnyPresence JustAPIs[12]
Amazon
Netflix[7]
SoundCloud[7]
The Guardian
Jelastic
Riot Games
Akana
Implementations[edit]
Spring Cloud
Seneca Microservices Framework and Protocol
MicroService4Net (C#)
Nirmata
Contents [hide]
1 Details
2 History
3 Philosophy
4 Criticism
5 Languages
6 Users
7 Implementations
8 See also
9 References
Details[edit]
Properties of the Microservices architecture:
The services are easy to replace
Services are organized around capabilities, e.g. user interface frontend, recommendation, logistics, billing, etc.
A microservices-based architecture
lends itself to a continuous delivery software development process.
is distinct from a Service-oriented architecture (SOA) in that the latter aims at integrating various (business) applications whereas several microservices belong to one application only
History[edit]
Wiki letter w.svg This section is empty. You can help by adding to it. (September 2014)
Philosophy[edit]
Philosophy of Microservices architecture:
The services are small - fine-grained as a singular business purpose similar to the Unix philosophy of "Do one thing and do it well"
The organization culture should embrace automation of deployment and testing. This eases the burden on management and operations
The culture and design principles should embrace failure and faults, similar to anti-fragile systems.
The services are elastic, resilient, composable, minimal, and complete.
[3] [4] [5]
Criticism[edit]
The microservices architecture is subject to criticism for a number of issues:
services form information barriers[6]
the architecture introduces additional complexity and new problems to deal with, such as network latency, message formats, load balancing and fault tolerance,[7] ignoring one of these belongs to the "Fallacies of Distributed Computing"
testing and deployment are more complicated[7]
the complexity of a monolithic application is only shifted into the network, but persists:
You can move it about but it's still there!
—Robert Annett: Where is the complexity?[8]
Languages[edit]
Jolie [9]
Vertx [10]
Users[edit]
Known users of the Microservices architecture:
Apprenda[11]
Cloud Foundry[7]
HP Helion Development Platform
Bluemix
AnyPresence JustAPIs[12]
Amazon
Netflix[7]
SoundCloud[7]
The Guardian
Jelastic
Riot Games
Akana
Implementations[edit]
Spring Cloud
Seneca Microservices Framework and Protocol
MicroService4Net (C#)
Nirmata
Comments
Post a Comment
https://gengwg.blogspot.com/