Mircoservice Architecture vs Service-Oriented Architecture (SOA)

It’s interesting how microservices are the new hype and SOA is detrending:

What’s the difference between the two? To me, the best description seemed to come from this StackOverflow answer:

So, SOA is an architectural pattern in which application components provide services to other components. However, in SOA those components can belong to the same application. On the other hand, in microservices these components are suites of independently deployable services.

A manifestation of this is for example, that often in SOA you’ll still just use one programming language, whereas in a microservice architecture you could choose the language that suits the service best.

So what do you think, are the trends justified or is it just because SOA is now “old” and Microservice Architecture a bit hyped? Leave your comments below.

One Reply to “Mircoservice Architecture vs Service-Oriented Architecture (SOA)”

  1. I would say (you’ve heard it a thousand times), choose the right tool for the job. For example a Latex Compiler or an image search or a print service could be perfect microservices. Other parts would be better suited just as libraries. There’s no silver bullet.

Leave a Reply

Your email address will not be published.