Actions

Microservices

Revision as of 21:25, 29 June 2021 by User (talk | contribs) (Created page with "== Definition of Microservices<ref>What are Microservices? [https://microservices.io/ Microservices.io]</ref> == '''Microservices''' - also known as the '''microservice archit...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Definition of Microservices[1]

Microservices - also known as the microservice architecture - is an architectural style that structures an [[Application}application]] as a collection of services that are:

  • Highly maintainable and testable
  • Loosely coupled
  • Independently deployable
  • Organized around business capabilities
  • Owned by a small team

The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack.


File:File.png
alt text


source: DZone


The microservice architecture is not a silver bullet. It has several drawbacks. Moreover, when using this architecture there are numerous issues that you must address. The microservice architecture pattern language is a collection of patterns for applying the microservice architecture. It has two goals:

  • The pattern language enables you to decide whether microservices are a good fit for your application.
  • The pattern language enables you to use the microservice architecture successfully.

A good starting point is the Monolithic Architecture pattern, which is the traditional architectural style that is still a good choice for many applications. It does, however, have numerous limitations and issues and so a better choice for large/complex applications is the Microservice architecture pattern.


What Microservices are Not[2]

Microservices might also be understood by what they are not. The two comparisons drawn most frequently with microservices architecture are monolithic architecture and service-oriented architecture (SOA).

The difference between microservices and monolithic architecture is that microservices compose a single application from many smaller, loosely coupled services as opposed to the monolithic approach of a large, tightly coupled application

The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)}enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.

  1. What are Microservices? Microservices.io
  2. What Microservices are Not IBM