michael-dam-mEZ3PoFGs_k-unsplash.jpg
blocshop
September 25, 2020
0 min read

SOA versus microservices: 6 big differences explained

SOA versus microservices: 6 big differences explained.jpeg

What is Service-oriented architecture (SOA)?

Service-oriented architecture (SOA) debuted in the 1990s. Its goal was to address the problem of ever-growing codebases and complex systems. The idea was to break these up into components that would deal with specific business objectives. Focused on the enterprise level, SOA is based on the concept of reusing software and code to avoid waste.

What are microservices?

Microservices architecture can, at first glance, seem very similar to SOA. It also has the goal of breaking up monolithic applications into components. A core difference is that microservices do not need to fulfill enterprise-wide requirements. Each microservice does what it does and does it well, without worrying about how it fits into the bigger picture.

Read about how to convert a monolith to microservices in this article.

What are the advantages of microservices architecture over SOA?

Microservices architecture in some ways evolved from SOA, or at least was able to learn from the mistakes made, and benefit from new practices and technology, including agile approaches to software development.

Microservices are faster, more robust and reliable, easier to deploy and scale, and just plain leaner than any SOA. Teams are small and independent and there is a refreshing lack of interdependencies that lives up to the initial dream of SOA and takes it to a new level.

Read on for six reasons why the microservices of today are nothing like the SOA of yesterday.

6 big differences between SOA and microservices

1. Communication

How SOA and microservices architecture communicate is one of the starkest illustrations of the differences between them. Each service in SOA must use the enterprise service bus (ESB) to communicate with other services. This should standardize and simplify communications with a single, centrally managed system. But it also means that the ESB acts as a bottleneck to development, with updates and integrations for components ending up queued. Microservices instead use an API layer, an approach that relies on simpler, and quicker, exchanges of information between separate components.

2. Granularity

The services in SOAs can be big or they can be small. They can even be massive and shared across the entire enterprise. SOAs were never designed to be as small as possible, so the services used can be considered coarse-grained in terms of granularity. Both the scope and size of the service can be vast, with shared databases, and multiple interdependencies. On the contrary, microservices are designed to be highly focused and fine-grained. Small teams, faster onboarding for new hires, fewer potential points of failure.

3. Coupling and cohesion

When you have small, specialized services, you can afford to have low coupling and high cohesion. Each microservice is based on the idea of “bounded context”, in other words, it is self-contained, with as little sharing of components, data, or interdependencies as possible.  This results in high cohesion, which means that the origin of problems can be rapidly identified as arising from a specific microservice. This component can then be isolated and fixed. In SOAs, despite the stated goal of loose coupling, the sharing ethos proves to be a vulnerability. Not only can there be an impact on speed, but faults can be harder to trace and fix.

4. Reuse

Reuse of components is built into the philosophy behind SOA, with shared services prioritized in importance over highly specialized implementations. Because of the enterprise-level focus of SOA, sharing is evaluated as reducing waste, saving time and money. Unfortunately, this misses out on a big part of the whole picture, where sharing also creates vulnerable interdependencies and slows down development. Microservices take into account that it is usually better to work with smaller components and keep everything separate. If you reuse something designed for another purpose, not only will you be dependent on its development schedule, your component will fail when it fails. If microservices need to reuse code, the preference is to duplicate it and disconnect its development from the original.

5. Data duplication and storage

Building on the concept of reuse, SOA usually prefers to share data. This extends to the sharing of databases between components. All services must access and change data that is effectively stored in a central source. This reduces the need to duplicate data, but it can result in speed problems and inevitably leads to interdependencies between services, as there must be agreed-upon protocols for how the data is stored and accessed. In contrast, microservices use whatever data storage is best suited to the task and aren’t shy about duplicating data whenever necessary. While this can add complexity in terms of data management and keeping everything up to date, the speed boosts of having local or exclusive access to data mean that microservices again win out over SOA.

6. Deployment

The focus on keeping microservices separate and small means that the teams can be smaller. These independent teams can work at differing paces and deploy their modules without worrying about the deployment schedules of other teams. They can even progress to continuous deployment, with the feature and bugfix pipelines reaching the end-user much faster than ever before. SOAs, on the other hand, suffer from the kind of deployment issues that plague monolithic systems. If you add or change a service, the entire application needs to be redeployed.

Are microservices a subset of SOA?

Both service-oriented architecture and microservices deal with the concept of converting monoliths into discrete modules. SOA came first, so it might seem natural to think of microservices as a subset of its predecessor. But SOA was designed to enable different applications of varying sizes to communicate, whereas microservices come together to form a network of small modules that can be considered an application. SOA is in some ways still stuck in the mindset of the monolithic era, with coarse-grained, big services that are designed to share a lot of functionality. Microservices are leaner, more independent, and fine-grained. One way to think of the relationship between the two is that microservices architecture learned from the shortcomings of SOA and managed to deliver the promise of truly breaking apart monolithic applications.

How Blocshop can make microservices work for you

Blocshop has been breaking monoliths into microservices since the software architectural style got its name in 2012. We know our microservices and we can walk you through the process of deciding how to make them work for you. Contact us today for a project estimate or even if you just need something explained.

Free ebook: From monolith to microservices

From monolith to microservices (ebook): How to break a monolith application into microservices.png

Learn more from our insights

Top 15 micro-SaaS ideas for your startup in 2023.png
December 06, 2021

Top 15 micro-SaaS ideas for your startup in 2022

What exactly do we mean by micro SaaS? Micro Saas solutions use a web browser or mobile app interface. Micro SaaS solutions usually come about through the effort of an individual or very small team. It aims to solve precise problems. Micro SaaS projects have small budgets and overhead. Customers use Micro SaaS solutions on a monthly or yearly subscription basis. Micro SaaS projects target a small niche of the consumer market.

Software engineer hourly rates in 2021 (based on experience and location).png
November 22, 2021

Software engineer hourly rates in 2021 (based on experience and location)

Region influences salary more than any other factor. Taxes rates, cost of living, and government benefit programs affect the rates software developers charge. Software developers in the USA  and Canada earn more than software developers in other countries.

The best programming languages for app development in 2022.png
November 15, 2021

The best programming languages for app development in 2022

Software developers usually have three main ways to create an app. They can choose to code a native app, a hybrid app or a progressive web app. Developers create native apps to function on one specific platform, usually either iOS or Android. They create these apps using Swift or Objective C for iOS. For Android they use C++, Kotlin or several other languages. 

Cross-platform mobile app development: Tools & frameworks for 2022.png
November 09, 2021

Cross-platform mobile app development: Tools & frameworks for 2022

The cross-platform development project aims to create apps compatible with several operating systems. Cross-platform apps work on iOS, Android, and Windows. Cross-platform apps look and feel like apps developed specifically for the operating system.

App development cost breakdown in 2022.png
November 08, 2021

App development cost breakdown in 2022

Your business needs an app, but you aren’t sure about the cost of creating an app. Without some figures, you can’t even begin to estimate the potential budget, so let’s get you sorted with the information you need to make your app a reality.

unnamed.png
November 04, 2021

Web app development: a detailed guide

The best web apps give a responsive and engaging user experience through a browser instead of a single application. Think of web app development as a super-charged website. Web apps have many features of mobile apps coded for iOS or Android without the need to code for specific platforms. Developers create web apps using HTML, javascript, Python and CSS.

15 useful web app development tools for 2021.png
October 29, 2021

15 useful web app development tools for 2022

Web development vs app development: Choose the best for your business.png
October 19, 2021

Web development vs app development: Choose the best for your business

Outsource web development in 2021 and beyond: benefits & tips.png
October 15, 2021

Outsource web development in 2021 and beyond: benefits & tips

8 IT outsourcing trends in 2022.png
October 11, 2021

8 IT outsourcing trends in 2022

More and more firms choose to outsource their IT operations and functions. IT outsourcing grows each year. The Gartner report announced that firms spent $3.8 billion dollars on IT outsourcing in 2019. They expect that the trend will continue. Companies aiming for digital transformation need partners and tools. They need tools that they cannot build in-house with speed and accuracy. 

In-house development vs outsourcing software development.png
October 01, 2021

In-house development vs outsourcing software development

Every business starting software development must ask themselves what will serve them better, in-house or outsourcing? There is not a simple answer to the question. Making the choice to develop in-house or to outsource will have long-term consequences.

16 Software development project ideas.png
September 17, 2021

16 Software development project ideas

Every startup needs a great idea. Something unique and compelling. Startup businesses succeed when they find a customer need that they can fulfill. Startup businesses and independent software developers constantly search for just such needs.

Software development budget estimation.png
September 16, 2021

Software development budget estimation

An unlimited budget would make many teams very happy. But that approach has pitfalls. If the team works without much oversight or customer input, they may waste money. They might create features that the customers won’t use.

What are the differences between Agile and Waterfall?.png
September 07, 2021

What are the differences between Agile and Waterfall?

These days, most software development teams choose Agile methodology to organize their work. The Agile vs. Waterfall debate still rages, though. Many people question whether Agile works better than Waterfall in all circumstances. Does Agile deliver great ROI? Does Agile help teams work faster? Let’s take a close look at both Agile and Waterfall. We will examine the merits and drawbacks of each approach.

unnamed.png
September 06, 2021

Converting Story Points to Hours: Why Doesn't It Work?

In traditional software development, teams would describe the amount of work they had in hours. But Agile software development teams have a better way. Agile teams use Story Points to estimate the work they have ahead of them. Let’s take a closer look at Story Points and hours, and examine the benefits of Story Points.

Scrum vs. Extreme Programming (XP): What's the difference?.png
September 02, 2021

Scrum vs. Extreme Programming (XP): What's the difference?

We've covered the Software Development Life Cycle (SDLC) and the Agile development framework. Now it's time to look at different methodologies and approaches to their implementation. There are several, but we'll focus in this article on just two of them, Scrum and Extreme Programming (XP). We'll look at the differences between them and how they can even be used together for even better results.

The Scrum Sprint cycle explained.png
September 01, 2021

The Scrum Sprint cycle explained

Agile Scrum teams break down large development projects into small bursts of activity, called Sprints. A Sprint in Agile is a short, time-boxed period where a software development team completes work. They choose which items and fixes they will tackle in Sprint Planning Meetings. The Sprint cycle sits at the very center of Agile methodology. 

Use Cases vs. User Stories: relationships and differences.png
August 12, 2021

Use Cases vs. User Stories: relationships and differences

Product Backlog prioritization techniques & tips.png
July 27, 2021

Product Backlog prioritization techniques & tips

Software development project management guide.jpeg
July 26, 2021

Software development project management guide