Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Weblogic, Microservices Expo

Weblogic: Article

The Triumph of the Ho-Hum SOA

Big paradigms creep up on us until they become an omnipresent fact of life

SOA and WOA Magazine on Ulitzer

If you've followed the arc of the SOA revolution, you might have expected the current moment to be one of great fanfare and proclamations of success. SOA (was supposed to have) arrived! SOA (was supposed to be) an accepted standard for software development and enterprise architecture. Yet, as we have seen, the naysayers appear to have had their day. SOA is DOA, we are told again and again. The recession/complacency/complexity/security problems/creeping vendor lock-in, you name it, has put a dagger in the heart of the enterprise SOA. I don't think it is actually thus. The reality turns out to be more subtle, and the declaration of SOA's demise is premature.

Nearly a decade after the debut of the Web services standards and the modern service-oriented architecture (SOA), the proof of the paradigm's remarkable success lies in what can only be described as its rather quiet and dull but effective existence. SOA has become so omnipresent, so unsurprisingly effective, it's a triumph. While many large organizations have been planning and executing far-reaching SOA plans, a different reality has snuck up on everyone. Service-orientation, if not actual SOA, is simply embedded into most software today, and it is routinely pulling off what used to be considered a nearly impossible task: the seamless, low-friction interoperation of radically different applications.

Like the hundreds of invisible electric motors that run our homes, tools, and offices, Web services are now stealthily powering whole classes of enterprise technology. They're like mobile phones. We just assume everyone has one today. And, like the mobile phone experience, which was total science fiction a generation ago but today is so commonplace it's not even noticed any more, Web services are the remarkable, nearly invisible magic in current integration scenarios.

I see this constantly in my work at Mitratech, whose TeamConnect software is used to manage corporate legal and compliance departments at large companies. Regardless of whether our clients have developed the kind of full-blown, enterprise SOA that everyone had on the drawing board circa 2005 or not, we are consistently implementing Web services-based integrations to other enterprise applications. What's fascinating is how Web services and the service-oriented capability are just assumed to be available. If you're deploying software in a large enterprise, you can pretty much assume that you can plug your other application in to Web services in the application infrastructure and that it can discover and integrate with other applications via their Web services.

Like many other packaged software vendors, we regularly plug TeamConnect into Web services interfaces in other applications and create integrations in days, which would have surely taken weeks or even months at the turn of the century. It's all, so, wonderfully boring! That's true success for SOA. Service-orientation, and Service-Oriented Business Applications (SOBAs), if not actual SOA, have taken over so completely in enterprise architecture for integration purposes that it's just not a big deal any longer, it's a fact.

For example, we often connect our corporate legal matter management product suite with enterprise content management solutions. This is done via web services calls that create the corresponding folder in the DM when the matter is created, another web service call to share security rights information, and presto they are working like one composite application. It's not a hassle to accomplish this integration. In fact, the integration potential is essentially pre-packaged into both solutions. Each vendor already knows where the integration is going to occur so it's already there. There's no consulting of a massive, central UDDI or federated bank of Web service registries, and no ESB. In contrast to the big vision, we now have narrowly scoped but highly valuable service-oriented business applications (SOBAs). How's that for dull?

One thing that is striking, though, is how different the reality of SOA is turning out to be in comparison with the way it was envisioned in 2001. As the SOA "revolution" gained momentum in the heady days of 2003-2005, the big vision was that major organizations would launch a service-oriented architecture program across the entire enterprise. With a large-scale UDDI at the core, developers would access Web services using ESBs and similar business process management / modeling technologies. Developers were to use existing Web services to build composite applications assembled out of odd Web services strewn across the enterprise, and to develop their own Web services on top of legacy applications. Of course, some of this has happened, but what seems to be more common, and a lot more interesting in its own boring way, is the simple, nonchalant hooking up of Web service-enabled applications as requirements demand it. It seems as if the preference for packaged applications with exposed Web services has outstripped the early SOA vision of a universe of custom-developed Web services being tied together in wholly new composite apps.

Consider what "code reuse," the rallying cry of the SOA movement, looks like in the successful, ho-hum SOA. The code-reuse theory was based on the idea that you could develop a Web service once and use it many times. That is true, but what's really happening is the repeated reuse of services from packaged software offerings. It's more like "buy once, use many times." Again, it's more boring than developing your own services, but still a great economy.

The ho-hum SOA has some catches, though. Broad, ad-hoc point-to-point Web service integration may advance the utility and value of service-orientation, but it can potentially wreak havoc on security and governance. In most cases, integrations occur between systems managed by consenting adults, who think through the data access control and confidentially issues as they plan and execute the connections. However, you can't make that assumption universally, and "self-policing" of app-to-app integration can be very problematic. SOA governance solutions can make a big difference here, but you need to have the right one and know that it will have the desired effect at a reasonable cost.

Data management can also get tricky when a lot of SOBAs are getting stitched together more or less on the fly. Part of a successful SOA technology strategy is making sure the information flowing through service-oriented applications is timely and accurate. Data that gets transformed on its way in and out of service-oriented applications can potentially cause disaggregation in the underlying databases unless SOBA development and data management are closely aligned. With SOA taking over, sans drama and major announcements, the IT department needs to keep up with this quiet tsunami, assuring compliance in information flow and integrity of enterprise services. Using ESBs to streamline the integration and to manage the X-Application Web services is an important factor of a large Enterprise / X-Enterprise SOA; this will ensure you publish the data once and subscribe from one or more systems, centralize common data transformations, establish common Business processes, share them, and so forth.

Though the big SOA plan and corporate SOA initiative are still important projects to work on, today's IT manager should not lose sight of what's actually happening, in SOA terms, right in their backyard. Historically, the winners of major technology battles are neither flashy nor loud. Big paradigms creep up on us until they become an omnipresent fact of life, even if no one's been looking. That appears to be happening with SOA. It's a transcendent, if boring, success. There's a lesson in this. The big vision is great to have, but sometimes, even if you never reach it, the technological future you want to build will catch up to where you want it to be on its own steam, and merits.

More Stories By Hugh Taylor

Hugh Taylor is the co-author of Understanding Enterprise SOA and Event-Driven Architecture: How SOA Enables the Real-Time Enterprise and the author of The Joy of SOX: Why Sarbanes Oxley and Service-Oriented Architecture May be the Best Thing that Ever Happened to You. He serves as Senior Director of Marketing at Mitratech, a Los Angeles based enterprise software company.

Comments (0)

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.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
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...
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...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
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 ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.