Micro-service architectures allow systems to be broken down into independent services. They differ from service-oriented architectures (SOAs), which have been around for about a decade for several reasons:
- They emerge from the search for practical agility and increased efficiency by precursors of Cloud Computing, such as Netflix, Amazon, Gilt or Airbnb.
- They are naturally adapted to the Cloud and unfold natively on Platforms as a Service (PaaS). This is the type of platforms on which they have historically developed and deployed, and they naturally exploit the benefits.
- They do not depend on a software publisher solution, such as Enterprise Service Bus (ESB), and minimize software integration needs (EAI) with sophisticated functionality (mediation, service orchestration, etc.)
After several years of software development and maintenance, some enterprise applications are laborious and too expensive to evolve. This often leads to a clean sweep of past developments and rebuilding them from scratch. The rise of micro-services architectures (micro-services architectures - MSA) answers this problem and proposes ways to solve it.
In this Paper you'll discover:
- Objectives of micro-services architectures
- What are the characteristics of micro-services architectures
- Decoupling between micro services
- Key benefits of micro-services architectures
- Challenges raised by micro services
- Integration of micro services