eBook-Taking Enterprise Application Integration Cloud

This is a collection of eBooks published by Dell Boomi. They provide insights and advice about application and data integration.

Issue link: https://resources.boomi.com/i/1039571

Contents of this Issue


Page 0 of 1

Rev.3081120111154 Copyright 2011 Dell, Inc. All rights reserved. Taking Enterprise Application Integration Into The Cloud By: Bob Moul, General Manager, Dell Boomi If you're like a lot of CIOs, you've been in this business a long time and have pretty much seen it all. From mainframe to mid- range to client-server to ASP and everything in between. It's hard not to look at SaaS and cloud computing as just another fad – another name for things you've been doing for years. But as was the case with the advent of the internet, there are some fundamental transformations occurring in cloud computing that would be detrimental to ignore. The emergence of cloud- based integration platforms is one of those shifts. The reputation that integration has garnered over the years as an ugly, unwieldy problem is almost entirely due to the way integration software was previously built and delivered as opposed to the actual integration projects themselves. Ironically, the integration industry has created much of its own complexity. Fortunately, the SaaS model has led to a fundamentally different way of thinking about application design and delivery – one that makes possible a new and vastly more efficient model for delivering integration – even if you are not engaged with cloud computing or using SaaS applications. Genesis of Complexity Integration by definition is a distributed function. Applications run on multiple systems in multiple locations using multiple databases and files. Data are distributed. Infrastructure is distributed. Networks are distributed. Users are distributed. Therefore, integration processes also need to be distributed – executing in any number of places where integration of systems is required. In the traditional model of developing software, the approach was to build a standalone application (or suite) and then commercialize it by selling copies of that application to as many customers as possible. In today's cloud parlance, this is called a multi-instance, single tenant application – multiple copies of the same application with no shared resources. In this model, as the number of copies and versions of the application increase, the support costs increase dramatically while the innovation cycles come to a near standstill. Vendors spend more and more of their time and resources maintaining existing application code as opposed to delivering new features and functionality and yet continue to charge 20% or more in annual maintenance fees. At the same time, significant burden is placed on the end customers who have to maintain their copy of the application with new releases, updates and code patches. It is this maintenance challenge and fear of breaking hard-coded integrations that often keeps customers from upgrading. Enterprises are forced to spend 80% of their IT budget on maintaining current applications systems, and only 20% on new innovation. Implications for Integration When the multi-instance, single tenant model is applied to the world of data and application integration it inherently creates a number of complexities, such as security and governance challenges, that have plagued the industry for decades. Here's why. The functions involved with integration include designing and building the integration process, deploying the integration, executing the integration, and then ongoing monitoring and management. While the execution of the integration needs to be distributed at multiple points throughout the enterprise, ideally all other functions, e.g. administrative functions, should be centralized. However, vendors of integration products, using the traditional model of developing software, built all administrative and execution functionality into one product. Customers would then purchase a copy of an integration product (or even multiple products) for every instance where an integration process needed to run within the enterprise. It is typical for a large enterprise to be running 20 copies or more of these integration stacks in order to meet their business requirements. The impact of the above scenario was that not only was the necessary runtime distributed across the enterprise, but the functionality to build, deploy and manage the integration processes was also replicated across the enterprise. Having multiple instances of what would ideally be centralized administrative and management functions created a maintenance nightmare and weakened governance and controls. Nearly every major integration challenge – including version control, data visibility, auditability, policy enforcement and governance are the result of this legacy style of software development and deployment.

Articles in this issue

Archives of this issue

view archives of eBooks - eBook-Taking Enterprise Application Integration Cloud