Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Yeshim Deniz, Elizabeth White, Stackify Blog

Related Topics: Microservices Expo

Microservices Expo: Article

The Scaling Crisis Around SOA

Scalable SOA solutions are emerging

Making solutions scale is nothing new. However, the SOA technology and approaches employed recently are largely untested with higher application and information and service management traffic loads. SOA implementers are happy just to get their solutions up and running, but, in many cases, scalability has simply not been a consideration with SOA, nor is load testing, or other performance fundamentals for that matter. We're seeing the results of this neglect now that SOA problem domains are exceeding the capacity of their architectures and the technology in many instances.

My daily routine is to answer e-mail from somebody, somewhere, asking me why his SOA doesn't scale. Unfortunately, the answer is something these people don't want to hear. It's really the fact that they took the wrong approach, used the wrong technology, and the fix is going to be painful. However, you can avoid these issues just by doing some additional planning and testing upfront before you commit to a solution.

The core issue is that many SOA technology vendors haven't focused on scalability in their solutions. Instead, feature/function enhancements are the rule of the day. It's more important to add orchestration features and more adapters to your solution than to figure out how to pump more information, and manage more services. So these single-threaded solutions, on top of the issues around Web Services in general, make for solutions that are more about integration than true business transaction loads. Not to mention supporting the notion of both reuse and agility.

Its dependence on the traditional architectures is the core problem of scaling SOA solutions. The most popular SOA technologies require that all information and services under management do so in a single server domain (in most cases). This processing is a mixture of service abstraction, service management, schema and content transformation, rules processing, message splitting and combining, as well as message routing (ESBs). This is despite the fact that Web Services, at their essence, are more about the distributed service invocation model that's not as well followed when considering instances of technology. Indeed, most SOA solutions out there are bound to a single service approach, and don't provide a smooth path to scalability.

While the scaling crisis around SOA isn't well known at this point, considering the fact that the larger SOA projects have just started moving, there are a few vendors that I've been watching that provide the distributed architecture needed to bring better distributed reliability to SOA. Rogue Wave's HydraSCA, for instance, provides a service grid based on "Software Pipelines," an architecture and methodology that enables the development and deployment of scaleable SOA-based applications. Rogue Wave is promoting Software Pipe lines as a cross-vendor approach to service distribution, and other key players are in there as well using similar implementation patterns.

What's interesting is that Software Pipelines, the approach and the instance of Hydra technology, increases scalability by providing concurrent computing of business services in and across servers, while preserving business rules. For those of us who have been in the business for a while, this is common sense scalability, meaning that the processing is distributed across more than one processing entity, and so the throughput increases using this parallel processing model. As long as this distribution is managed well...it's very effective.

There are other SOA solutions moving in this direction as well, and as SOA becomes more accepted, the ability to make your SOA scale is clearly going to be on the critical path. What's key is that those who select SOA technology that needs to scale consider the following basic principles:

  • Consider performance and scalability as something that's systemic to the architecture; it can't be an afterthought.
  • Make sure to do a proof-of-concept to demonstrate that the technology works as advertised, and work with the vendor to understand the best way to implement the technology.
  • Consider operational issues during the design. Who's going to maintain it, and how?
  • Learn how to do basic performance and scalability modeling. While never perfect, they do indeed provide you with a jumping off point when considering high performance and scalable architectures.
  • Never be afraid to change approaches and technologies if they don't seem to be working out.

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
Gautam Warrier 09/04/07 02:24:56 AM EDT

As usual, Dave's comments are spot on...however, I worry more about getting the fundamentals right...Classical SOA vs SOBA oriented adoption. The more I observe the underlying challenges of technically deploying a SOA paradigm, I feel that we are not really comprehending the core issue here: Service Design & Process Orchestration. This problem grows exponentially with the Scale of the enterprise. At the same time, it begs the Question: do we have the right skills/experience in place to handle the mammoth task of Architecting a cross-organization/cross functional system landscape for a Classical SOA implementation or even does it make sense to even attempt such expertise. I would venture to propose that the answer is an arguable NO to both, we do not have the necessary background amongst our Enterprise Architect community to handle this "undefined" monster - dynamic & evolving standards/capabilities. And unfortunately, like Dave mentions if you don't get it right at the outset, refinement through iterations is a dangerous journey to undertake - it only aggravates the core issues. Ergo, I am leaning towards an approach (SOBA) that has devoted more energy in the Service Designs upfront & focuses on Business process flexibility while compromising on specific technical components. This also makes the monster manageable by the three key members of the initiative: the SOA architect, the Business Architect & last but not the least by any means, the Enterprise Architect.

@MicroservicesExpo Stories
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
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...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., 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.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
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...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"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.
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 ...