User Avatar

Developer Advocate at Tanzu by Broadcom focused on Kubernetes and Spring related technologies.

SOA Dreams, Microservices Delivers
Cora Iberkleid 🚢

I read an article today positioning Service Oriented Architecture (SOA) and Microservices as two architectural options, and the neutrality of the article surprised me, especially considering it was written a short year and a half ago.

Perhaps I'm oversimplifying, but I've always seen Microservices as an evolution of SOA, not an alternative. SOA had dreams. Big dreams! And Microservices made them possible.

SOA Dreams

Back in the '90s, developers realized that turning spaghetti into tortellini enabled better development practices and cleaner, more maintainable, and more reusable code.

The problem was that they could only do this in their own kitchen. In order to deliver the tortellini to the dining table, they had to mush all of them together—meat tortellini, cheese tortellini, potato tortellini—into a single, mushy ball so that they could be hoisted onto a big shared platter for everyone. In tech terms, monoliths were separated into services that were then bundled together into a single .ear file and deployed into a shared application server. Any potential benefits of separating services at runtime were promptly stunted.

Microservices: Livin' the Dream

Two things that still amaze me about microservices:

  1. They flipped the script. Rather than one app server for a bunch of tortellini, each tortellini was equipped with its own tiny, personal app server. Brilliant!

  2. They standardized. This opportunity was provided by the invention of Docker and container runtimes, all the way to Kubernetes. Tortellini matured into ravioli, all cut into the same beautiful shape and equipped with everything they needed on their journey to production—OS, runtime, app... all of it.

The dream of loosely coupled, composable services that can be deployed and scaled independently was now a reality not only for developers, but also for their operations counterparts. Everything became simpler, everyone became more agile, and this new reality has made way for new and bigger dreams.

Final Thoughts

SOA was more than simply breaking down monoliths, but I personally cannot separate SOA as an architecture from the technological limitations of its time because these limitations were also inputs into the ideas of SOA. Reevaluating SOA within the context of modern technology can provide value, but using the term SOA like it's the early 2000's, ignoring the broad and transformational impact of containerization on industry practices and innovations—from microservices to Kubernetes and beyond—eludes me.