Welcome!

Microservices Expo Authors: TJ Randall, Liz McMillan, Elizabeth White, Pat Romanski, AppDynamics Blog

Related Topics: Microservices Expo, Industrial IoT

Microservices Expo: Article

SOA Editorial - A Little Help from My Friends

SOA is not just technology, it's philosophy, organizational change, and business transformation

It's sometimes funny to write about service-oriented architecture. One of the things I say often and believe is that you can't buy a service-oriented architecture. SOA is not just technology, it's philosophy, organizational change, and business transformation. There's no place to buy that kind of dramatic, deeply impacting change.

The funny part, at least to me, is that you can, however, buy or acquire a good deal of infrastructure to set this up from a single source. In the industry, we call that a platform. And that's what this month's issue is about - SOA platforms.

Service-oriented architecture is a powerful concept - at its base, it replaces the concept of an application with the concept of a service. This isn't trivial. For 40 or more years, we've dealt with computers in the context of applications (I've left a few years off my count to account for the years before operating systems when we were really talking about programs, or code). We have the context of an application firmly established - people go to their computers, interact with applications, and do work.

SOA is about the next phase of computing - enabling computers to do some of the work unaided (computer-to-computer interaction), and freeing the user from having to interact with application after application to get work done. Anyone who's ever dealt with a call center and had to wait on the phone while the call center representative said, "Now give me just a minute, I have to bring up another application to do that," knows how frustrating, time-consuming, and challenging the traditional application-centric approach can be. Services (and the composite applications that no longer require the user to switch between applications to do a single business process) are the way we plan to break the tyranny of the application and take back control of the computer.

Services don't exist in a vacuum. Part of the chicken and egg problem we have in moving from applications to services is that services make only a limited amount of sense in the context of a single application, so there's not a strong impetus for application developers to use a service-based approach toward design when creating applications. Similarly, when you take a holistic view of the enterprise, you don't necessarily see the catalog of services you'd like to have to really establish a true architecture, and derive the highest value from composing processes from services.

That's where a platform becomes the middle ground and the way out of the chicken and egg problem. By establishing a platform for the enterprise, you can start to drive applications toward becoming services. A platform should provide discovery, registration, an ESB at the minimum, with most platforms also including security and management services as well. When you start to build your applications (or buy them specifically for the platform in many cases) to take advantage of the service orientation of the platform, you start to realize the advantage of the platform, and move past the challenge of service-enabling applications.

It also underscores the importance of getting a strong platform, one where the parts all work together well. You may not want to get everything from a single source or, depending upon your enterprise needs, you may not be able to do so. A soup-to-nuts infrastructure out of the box from a single vendor is not necessarily nirvana anyway, as those of you who've had the best-of-breed discussions over the years can attest. What is important is establishing an SOA infrastructure, or platform, on which an enterprise can leverage its application portfolio. The platform enables the portfolio transformation that must occur in order to move from an application orientation to a service orientation.

So it's funny, even though I don't think you can buy an SOA, I definitely think you can acquire a platform, and you're much better off with one then without.

More Stories By Sean Rhody

Sean Rhody is the founding-editor (1999) and editor-in-chief of SOA World Magazine. He is a respected industry expert on SOA and Web Services and a consultant with a leading consulting services company. Most recently, Sean served as the tech chair of SOA World Conference & Expo 2007 East.

Comments (2)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
At its core DevOps is all about collaboration. The lines of communication must be opened and it takes some effort to ensure that they stay that way. It’s easy to pay lip service to trends and talk about implementing new methodologies, but without action, real benefits cannot be realized. Success requires planning, advocates empowered to effect change, and, of course, the right tooling. To bring about a cultural shift it’s important to share challenges. In simple terms, ensuring that everyone k...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, will discuss how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galer...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace....
"There is a huge interest in Kubernetes. People are now starting to use Kubernetes and implement it," stated Sebastian Scheele, co-founder of Loodse, in this SYS-CON.tv interview at DevOps at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...