Welcome!

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

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Containers Expo Blog, Agile Computing, @DXWorldExpo, SDN Journal

@CloudExpo: Article

Creating Harmony When Cloud and On-Premise Worlds Collide

Integrating data across diverse SaaS applications with existing on-premise solutions has proved exceptionally challenging

In recent years, IT departments have been confronted with the convergence of several highly disruptive trends that have fundamentally altered the enterprise IT landscape, particularly when it comes to how data and applications are managed. Mobility and the rise of BYOD (bring your own device), as well as the growth of social media and the electronic information it generates, have each proved transformative. But perhaps no shift has been more seismic than the adoption of cloud and SaaS-based applications led by CIOs who see the value proposition associated with outsourcing many complex IT operations.

However, integrating data across diverse SaaS applications with existing on-premise solutions has proven exceptionally challenging. To streamline this integration without slowing adoption, IT stakeholders are turning to cloud-based integration solutions that can curtail complexity and IT oversight while enabling organizations to better leverage their information capital to drive business objectives. Indeed, according to a recent report by analyst firm MarketsandMarkets, the global Cloud Brokerage Services (CSB) market is on track to grow from $1.57 billion in 2013 to $10.5 billion by 2018, a compound annual growth rate of more than 45% over the five year period.

In this article, we will provide advice to IT leaders for creating sustainable environments using hybrid integration between SaaS technologies and existing on-premise applications. We will also explore the top considerations for building out a successful cloud integration strategy that offers the scalability and flexibility to withstand fluctuations in enterprise data management needs.

Start by Asking the Right Questions
Over the past few years, "Cloud" has transformed from the buzzword of the moment - all the rage but lacking concrete definition - to an efficient, widely recognized enabler of scalable IT operations. Despite the increasing ubiquity and viability of the cloud delivery model, it's important to remember that cloud is not "IT in a box." No one cloud service provider can meet all the complex IT needs of a single organization. By and large, enterprises evaluate and onboard an array of purpose-built solutions from diverse cloud providers. As a result, the need to successfully integrate them not only with each other, but also with traditional on-premise application-to-application (A2A) and business-to-business (B2B) systems is critical. The multitude of complex integrations - A2A, B2B, and on-premise applications to SaaS/cloud applications, and cloud-to-cloud (C2C) - requires a clear-cut integration strategy.

A critical first step in developing an integration strategy is to ask and answer a few key questions, the first of which is "what problem is the integration solving?" While achieving streamlined integration between cloud-based systems like Magento, NetSuite, SAP, Ariba, and salesforce.com is one aspect of a full-fledged strategy, it's important to remember the challenge extends beyond cloud-to-cloud integration. In reality, what many people today refer to as "cloud integration" is actually hybrid integration - integration not only between cloud systems, but between cloud and on-premise applications. Determining the specific integration goal - whether it is strictly cloud-to-cloud, or a larger hybrid model - ensures the strategy scales to both immediate and long-term integration needs.

Once you consider what problem the integration will solve, it's important to consider how integration will solve the problem. As the number of systems to be integrated grows, the number of potential interface points expands exponentially, and traditional, manually driven point-to-point integration can quickly become overwhelming. Each time an individual application is altered, or a trading partner changes its specification interface, IT must review all external connections for potential impact. An upgrade cycle for a large ERP system may spawn dozens, hundreds, or even thousands of integration projects across several departments and external trading partners.

Continuing to rely on this point-to-point integration model will become untenable as cloud adds another layer of complexity to the integration landscape. In order to avert chaos, enterprises are actively leveraging integration to create an interconnected web that holistically addresses data management and integration challenges across all of these disparate systems and applications. If an integration strategy is designed with a broader goal in mind, it is much more likely that the same strategy can be leveraged not only to solve immediate integration challenges, but future demands as well.

Identifying where integration is needed and how it can benefit an organization is an important first step. But once the decision has been made to move forward, there are a few key considerations that CIOs must take into account to successfully build out a strategy with staying power.

Reading the Signs: Spotting and Addressing Complexity
Anticipating the areas in which integration complexity is most likely to arise is crucial to the development of a flexible, cost-effective integration strategy. The following are two of the usual suspects of which CIOs should be aware:

  1. SaaS APIs: Many cloud providers promise to deliver a simple-to-use web API, but this is rarely the reality. Specifications for many SaaS APIs can run into the dozens, if not hundreds, of pages long, and can be a major headache for internal teams unfamiliar with the nuances of integration. Moreover, APIs often evolve over time as SaaS applications evolve, generating a source of ongoing complexity.
  2. Data Translation: The potential for complexity, however, does not end once the APIs are successfully integrated. Translating data between different SaaS applications, as well as between SaaS and on-premise systems, can be challenging, and this translation should be factored into the complexity calculus. Data that is not properly translated will be rendered useless, and backtracking to fix the glitch can add time and expense to business-critical projects. As a general rule, a bug that costs one dollar to fix during development will cost 10 dollars to fix during quality assurance, and 100 dollars fix once in production. This backtracking approach can prove particularly brittle when new systems are added to the ecosystem.

A Long-Term Vision: Thinking Beyond the First Integration Project
Integration with cloud is often a daunting prospect, particularly for businesses just beginning to onboard cloud applications as part of their IT strategy. The immensity of a single cloud integration can produce tunnel vision for IT teams, who get so bogged down in an initial project that they fail to consider the long-term implications of the integration and how it will ultimately fit into the overarching IT architecture - a problem already amply demonstrated with the pitfalls of the point-to-point approach. However, the inevitable complexity of integrating multiple applications over time should be sufficient incentive to give any CIO pause before creating a strategy tailor-made for a single integration project.

Even though it will likely require greater upfront investment and effort, organizations must settle on a cohesive sourcing strategy for integration that meets their individual needs. There are three fundamental options for this strategy: a do-it-yourself (DIY) approach based solely on existing knowledge of on-premise software; a DIY approach using a customer-driven integration Platform-as-as-Service (iPaaS); or outsourcing integration entirely to a third-party integration brokerage provider. When determining which of these strategies to adopt, it is important to consider the following:

  1. First, consider the deployment timeline. As departments across the enterprise demand rapid access to new and greater functionality offered by diversifying SaaS applications, IT departments are under mounting pressure to test, procure and deploy these solutions. This is where a CSB can help speed things up based on their experience working with various customers, implementation scenarios and technologies. Even as deployment windows tighten, however, many businesses are only just beginning to build out core competency around integration. For those with the strictest timelines, the option to build out an internal integration function may have already passed, and it may become necessary to bring in a third-party integration provider. While some may initially view these external integration providers as a Band-Aid solution, working with a specialized integration broker can often be the best long-term solution, especially when it comes to cloud integration where existing IT teams may have less familiarity.
  2. Second, consider the cost for integration in the long term. As the complexity of cloud integration projects continues to increase, building out an internal team will require a capital investment in expert personnel and software. Although it requires greater initial investment, this relatively fixed capital expenditure may be a better use of resources for some organizations. For others, such a large capital expenditure may not be feasible or efficient. Outsourcing projects to an integration broker shifts the cost of integration as an operating expense, reducing or eliminating the up-front cost, and providing a more scalable, recurring cost-structure.
  3. Once these factors have been weighed, the next decision is: in-house or external? Although SaaS applications for both back-office systems and B2B processes can offer tremendous efficiencies, the coordination and integration required on the back end is no simple matter. While building out in-house integration capabilities is important for some organizations due to commercial or other business considerations, companies that choose this route must recognize it early and take a proactive approach to cultivating the expert staff and resources that will be required to effectively manage and complete integration projects. For those businesses that don't have compelling reasons to keep the integration function in-house, outsourcing may prove more efficient. Cloud Services Brokers (CSBs) have existing integration infrastructure that can be leveraged for rapid deployment, and can increase capacity on demand, offering scalability when and where it's needed most. CSBs also deliver experience and collective intelligence around integration that can offer efficiencies beyond what can be accomplished with internal resources alone.

The key criteria and requirements around data management continue to expand, and cloud integration is at the nexus of this expansion. By planning and executing a comprehensive integration strategy that can efficiently and consistently scale to the evolving integration requirements of the business - including traditional on-premise, back-office systems and cloud-based applications - IT can help ensure the long-term scalability and business success. Whether the decision is to bring integration capabilities in-house, outsource integration needs, or use some combination of both, the time to start developing a plan is now.

More Stories By Rob Fox

Rob Fox is Vice President of Application Development for Liaison Technologies, and the architect for several of Liaison’s data integration solutions. Liaison Technologies is a global provider of cloud-based integration and data management services and solutions. He was an original contributor to the ebXML 1.0 specification, is the former chair of marketing and business development for ASC ANSI X12, and a co-founder and co-chair of the Connectivity Caucus. Connect with Rob on Twitter: @robert_fox1

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
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.