Welcome!

Microservices Expo Authors: Elizabeth White, Liz McMillan, Derek Weeks, Pat Romanski, Karthick Viswanathan

Related Topics: Microservices Expo

Microservices Expo: Article

Are You SOA New School, or Old?

Why you need to know the origins of your technology

It has come to my attention that there are really two kinds of SOA technology vendors out there, old school and new school - each offering very different approaches to solving the SOA problem. I'm not going to mention any particular vendors, but you guys can guess who they are.

Keep in mind, what's important here is that not any particular approach or technology is correct, but that the approaches and technologies you employ match up with your requirements and business expectations. However, it's also important to understand exactly the type of technology you're going to leverage, including its core - that's the point I'm attempting to make here.

Old-School SOA Vendors
Old-school SOA vendors are those with "legacy" integration or application development solutions that "SOA-tized" their stuff, basically adding Web services interfaces, orchestration, governance, etc. I've been here before - you're working with an existing product and existing customers, and suddenly a new wave comes along. You have to keep up, thus you add another layer onto your existing product to make it a bit more acceptable to the market, and also maintain backward compatibility with your existing customer base. It's not easy.

Thus, these guys layer on top of the existing stuff or creating another layer of abstraction, hiding the core with new interfaces, management layers, and perhaps a repository. Some of the common characteristics of old-school SOA are:

  • The need for their underlying and legacy core technology in order for their SOA technology to function. This is a sure sign that there are dependencies on the older coretech. This is not bad unto itself, but could cause performance issues as you work down to the core from the abstraction and back again. You'll find that some of the existing vendors do this, but some do not, so make sure to try before you buy.
  • The product cannot deal with coupling, only cohesion. This means that the SOA solution relies on an asynchronous messing system for internal communications - in other words information-oriented integration - and can't deal with behavior or service-oriented integration. Thus, reusing service through this type of infrastructure can be problematic, if not impossible.
  • The need for backward compatibility with an existing base of users. Again, this is not a bad thing necessarily, but if your SOA product is trying to maintain a portion of itself as a proprietary subsystem, that could limit development going forward.
The upside to old school is that you're in a new market space with a minimal amount of redevelopment. That is the upside for the vendor, however. Moreover, these are typically well-known and established players.

The downside is that you could have an archaic product at the core, and it may not handle the new ways in which we're aligning systems today, at the service level and not at the information level alone.

New-School SOA Vendors
New-school SOA vendors are those with new products. Typically they are start-ups with fewer than 100 or so customers. They don't need to SOA-tize their products because they are typically built from the ground up with SOA in mind, doing both service- and information-based integration. However, there are advantages to starting with a new canvas, and some drawbacks as well.

The upside to new school is that you're getting a product that's built specifically for the application to an SOA. Moreover, these new guys typically solve a particular portion of the problem, such providing just the registry, development environment, or federated identity. They don't offer "all-in-one SOA solutions," which is good. To date, I've not seen a product that can do it all. The downside is that you're dealing with a new company that is going to change a lot in the next few years, in good ways and bad ways.

Conclusion
So, which school should graduate from? At the end of the day, it's really a matter of your problem domain and the problems you're looking to solve, that's for certain. However, I can say that the new school products have more applicability for the SOA space since they are specifically designed for that purpose. The old school products just seem like quick reinventions, many of which are limited by the existing core product. When building an SOA, you don't want limitations - it's hard enough as is.

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 (4) 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
SYS-CON Brazil News Desk 05/05/06 11:19:09 AM EDT

It has come to my attention that there are really two kinds of SOA technology vendors out there, old school and new school - each offering very different approaches to solving the SOA problem. I'm not going to mention any particular vendors, but you guys can guess who they are.

SYS-CON India News Desk 05/05/06 10:46:51 AM EDT

It has come to my attention that there are really two kinds of SOA technology vendors out there, old school and new school - each offering very different approaches to solving the SOA problem. I'm not going to mention any particular vendors, but you guys can guess who they are.

Mark Griffin 01/30/06 03:17:02 PM EST

David,
Good article but I have a comment with one statement - "Thus, reusing service through this type of infrastructure can be problematic, if not impossible". I think building a reliable, reusable Services infrastructure requires the use of messaging as opposed to making it more difficult. Making this happen without messaging requires a lot more effort on the architect's part especially given the state and support of the various messaging standards out there.

I think you are correct about the retrofit of existing platforms (we're talking about traditional EAI vendors right?). It has had a certain amount of pain associated with it but generally not in the messaging area. Plus companies have a lot invested in these systems. I think making them work as opposed to starting from scratch is the more realistic view.

markg
http://darth.homelinux.net

SYS-CON Belgium News Desk 01/30/06 11:06:53 AM EST

It has come to my attention that there are really two kinds of SOA technology vendors out there, old school and new school - each offering very different approaches to solving the SOA problem. I'm not going to mention any particular vendors, but you guys can guess who they are.

@MicroservicesExpo Stories
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
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...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.