Microservices architectures are very popular today. In this article, we take a look at how microservices architectures are different from Service Oriented Architectures (SOA).
Both Microservices and Service Oriented Architectures primarily talk about creating small services.
Whenever we talk of microservices, we refer to small sized services that are also independently deployable.
For example, we should be able to release Microservice1 without affecting the behavior of any of the other microservices. We would be able to take such a microservice to production very quickly.
The focus of SOA might be on creating independent services, but not exactly independently deployable ones. In SOA, while we focused on API, the deployable units were generally large.
Thin Pipes v Enterprise System Bus
With the evolution of its architectures, SOA ended up having large Enterprise Service Buses (ESBs). ESBs were introduced to enable loose coupling between SOA components.
In order to implement a new feature in an application, changes are needed both on the application logic, as well as in the enterprise bus.
The enterprise system bus become a central spoke where a lot of business logic also made its way. Over a period of time, these sucked in a lot of business logic, making the application difficult to maintain.
Microservices architectures keep minimum logic in the communication infrastructure - thin pipes.
Tied To XML
SOA was tied to the XML technologies, inheriting its formalities and complexities.
With SOA, there is always an centralize architecture team that decides what logic goes into an ESB, and what cannot, among other things.
On the other hand, microservices architectures focuses on having decentralized governance.
Let’s take an example
Consider a banking application. Along with a savings account, a customer gets a debit card for free. An Insurance Savings Account and a Debit Card are different banking products, managed by different product systems.
In the SOA architecture, the ESB takes the order from the selling application, and handles the communication with the systems that create the appropriate products.
The ESB ends up having a lot of business logic, making it top-heavy.
Typical microservices architecture makes use of an event driven architecture. It makes extensive use of a message queue to ensure reliable communication between different microservices, each having it own responsibility.
The sales app would create an order event, and put it in the queue. Each of the other services would look at the event, and process it if relevant to them.
In this article, we had a look at the differences between microservices architecture and SOA. We looked at independent deployability, de-centralized governance, and the event based nature of microservices architectures.
Introduction to Cloud, Microservice - Challenges and Advantages
This is the article in a series of five articles on cloud and microservices:
- 1 - Microservices Architecutres - Quick introduction to Cloud - Why, What and How?
- 2 - Microservice Architectures - Introduction to Spring Cloud
- 3 - Microservices Architectures - Advantages Of Microservices
- 4 - Microservice Architectures - Challenges with building Microservices
- 5 - Microservices Architectures - Microservices vs SOA