Microservices Expo Authors: Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika, Liz McMillan

Related Topics: Microservices Expo

Microservices Expo: Article

SOA Vendors Focus Too Much on Integration . . .

. . .and not enough on architecture

We've all experienced the hype: "We're a SOA tool, and we're here to help!"

However, most SOA vendors out there don't understand the value of SOA, or even how to approach SOA. They focus on the tactical and not the strategic. Why? A tactical approach is easier for them to sell, and easier for them to understand. However, this approach means they are selling their customers short.

Take integration, for example. We've understood how to do integration since the early days of EAI, and, indeed, it's clearly a component of SOA. However, integration, on its own, is not architecture. Thus, just binding systems together is not architecture, thus it is not SOA.

The fact is that dozens of vendors built integration tools when integration was hot. As the world moved toward SOA, driven by the hype, vendors just relabeled their tools "SOA," even though they still address integration and not architecture. Therefore, when selling into the SOA market, they are driving integration and not architecture, focusing more on the tactical and not the strategic. There is not as much value to the business there.

While many think that just binding applications together, allowing them to share behavior and information counts as SOA, that's really not the case. SOA is the orderly management of many resources/services, and providing the ability to configure those resources into solutions, or, more important, reconfigure them as new solutions as the business requires. In essence, you create a platform for change, which is a much different notion than simple integration.

My advice to these vendors is to spend some more time understanding just what SOA is, and its value to the business. Integration is in there, but it's a small part of architecture. I should know, I wrote the book on integration. However, I did not attempt to see it as architecture. Vendors should not pass if off as that either.

But, of course, a few vendors and end users are pushing back on my advice, and here is some general guidance around the pushback.

  • SOA vendors don't need to understand architecture. They do indeed; this includes architecture in general, and "an architecture" specifically...yours for instance. When you're selling technology, it's a tad helpful if you understand its logical fit within the SOA. I'm surprised I have to keep explaining this, but there are those out there who think that tactical selling of this type of technology is the most productive approach. It's clearly not if you've seen the results. VDA, or Vendor Driven Architecture, is killing SOA. Not that the vendors are evil guys trying to trick end users, but the lack of architectural consideration, on both sides, means you will select the improper technology in many instances.
  • But, integration is important Dave. You bet it is, but it's not architecture; it's a part of architecture. Architecture is the orderly creation, placement, configuration, and management of IT assets, and integration is a core architectural pattern. Indeed, without the notion of integration, SOA would not do the job now, would it? Systems need communication at both the information (data) and behavior levels (service), including mediation of the different formats, semantics, protocol, and APIs. However, the more holistic concept is architecture, and you can't do integration without understanding the architectural context. This includes vendors and enterprise / SOA architects, working together.

I suspect that this won't be well received by the SOA vendors out there, based on the reaction from the last column in which I addressed this issue. However, it's tough love. You better figure out how to sell technology with the heart of a teacher, and not the heart of a salesman, else you'll discover that your customers won't find you helpful in the long run. The good vendors understand that, and end users really should ask the tough questions up front.

More Stories By David Linthicum

Dave Linthicum is Sr. VP at Cloud Technology Partners, and an internationally known cloud computing and SOA expert. He is a sought-after consultant, speaker, and blogger. In his career, Dave has formed or enhanced many of the ideas behind modern distributed computing including EAI, B2B Application Integration, and SOA, approaches and technologies in wide use today. In addition, he is the Editor-in-Chief of SYS-CON's Virtualization Journal.

For the last 10 years, he has focused on the technology and strategies around cloud computing, including working with several cloud computing startups. His industry experience includes tenure as CTO and CEO of several successful software and cloud computing companies, and upper-level management positions in Fortune 500 companies. In addition, he was an associate professor of computer science for eight years, and continues to lecture at major technical colleges and universities, including University of Virginia and Arizona State University. He keynotes at many leading technology conferences, and has several well-read columns and blogs. Linthicum has authored 10 books, including the ground-breaking "Enterprise Application Integration" and "B2B Application Integration." You can reach him at [email protected] Or follow him on Twitter. Or view his profile on LinkedIn.

Comments (1) View Comments

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.

Most Recent Comments
09/12/08 11:09:34 AM EDT

Trackback Added: The Problem with SOA is Architecture; As I read David Linthicum's post on SOA vendors focus too much on integration... and not enough on architecture, this really clarified one of the messes we've gotten into with SOA. The problem is architecture. Dave's definition of architecture (from the post) is:the orderly creation, placement, configuration, and management of IT assets.The problem is that it's only one definition of

Microservices Articles
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
Containers, microservices and DevOps are all the rage lately. You can read about how great they are and how they’ll change your life and the industry everywhere. So naturally when we started a new company and were deciding how to architect our app, we went with microservices, containers and DevOps. About now you’re expecting a story of how everything went so smoothly, we’re now pushing out code ten times a day, but the reality is quite different.
Traditional IT, great for stable systems of record, is struggling to cope with newer, agile systems of engagement requirements coming straight from the business. In his session at 18th Cloud Expo, William Morrish, General Manager of Product Sales at Interoute, will outline ways of exploiting new architectures to enable both systems and building them to support your existing platforms, with an eye for the future. Technologies such as Docker and the hyper-convergence of computing, networking and...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...