Difference between revisions of "MicroService"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
''The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. While there is no precise definition of this architectural style, there are certain common characteristics around organization around business capability, automated deployment, intelligence in the endpoints, and decentralized control of languages and data. '' |
''The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. While there is no precise definition of this architectural style, there are certain common characteristics around organization around business capability, automated deployment, intelligence in the endpoints, and decentralized control of languages and data. '' |
||
| − | http://martinfowler.com/articles/microservices.html |
+ | * http://martinfowler.com/articles/microservices.html |
| + | * http://martinfowler.com/bliki/MicroservicePrerequisites.html |
||
| + | * http://martinfowler.com/articles/distributed-objects-microservices.html |
||
=Livres= |
=Livres= |
||
Latest revision as of 15:32, 7 May 2015
The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. While there is no precise definition of this architectural style, there are certain common characteristics around organization around business capability, automated deployment, intelligence in the endpoints, and decentralized control of languages and data.
- http://martinfowler.com/articles/microservices.html
- http://martinfowler.com/bliki/MicroservicePrerequisites.html
- http://martinfowler.com/articles/distributed-objects-microservices.html