Buyer's Guide

Application integration software: A buyer's guide

A collection of articles that takes you from defining technology needs to purchasing options
Manage Learn to apply best practices and optimize your operations.

When do you need an application integration strategy?

In this article, Tom Nolle explores the many needs a company has to justify an application integration strategy and software purchase.

Application integration is a trend with drivers as diverse as businesses. So, the question shouldn't be whether you, as the software decision maker, need application integration, but why you think you don't. Diversity in business size, type, products, services and workers could mean that some IT trends don't apply to some businesses. You may not think that you need an application integration strategy, or that it doesn't fit your organization.

This article discusses the various cases where an application integration strategy proves a necessity for enterprises. As companies transition from a manual model to an IT model, and information travels from one application to another among employees and with suppliers and customers, application integration has become a more vital IT force.

The desire for more agility in business practices, the componentization of application software and cloud computing are three trends today that are affecting companies. It's the combination of these trends that affects you, that will set the importance of application integration and define your best path forward. That means you'll have to assess how each of these trends will likely affect your company. And that's easiest to do by tallying your "Yes" answers to a group of questions about each of the trends.

How agile is your business?

Business agility seems a given; who wouldn't say they wanted to be agile in response to opportunities, issues and competition? The question is whether the response is likely to involve a change in the movement of work among applications. Ask yourself the following questions:

  1. Do you pass any work directly between applications today?
  2. Over the past two years, have you purchased or developed new applications based on changes in your business?
  3. Does your company face changes in its product or service lineup, or changes in competition?
  4. Is your business highly regulated and expected to respond to regulatory changes quickly?
  5. Do you expect changes in business status, such as incorporation, mergers and acquisitions, or operating geography?

Componentization is a driver for application integration

The second driver for an application integration strategy is more technical. We tend to think of IT applications as software packages, implying that they're a self-contained unit. In fact, software development practices have long favored modularization or componentization of software to lower development cost and risks. When considering the user, organizations can also use componentization to duplicate application elements to increase reliability and improve performance under variable activity loads.

To determine the likelihood that componentization is a driver for application integration in your company, ask the following questions:

  1. Does any of your current software -- developed internally or purchased -- utilize or even offer scalability or resiliency through the use of multiple software copies?
  2. Do you use load balancing or application acceleration in your current applications?
  3. Do you plan to develop or purchase a major new application shortly -- one that involves information sharing with your current applications?
  4. Does your company develop a lot of its current software internally?

Cloud computing complicates the decision

The final application integration driver is cloud computing. And because of the glow of publicity surrounding the cloud and the variety of ways applications can be deployed there, this driver may be the most difficult to assess.

The most important thing to remember about cloud computing is that it will complicate any application integration strategy created by any other driver or combination of drivers. That means that cloud plans are likely to force businesses that answered "Yes" to a single question on the other drivers to treat themselves as being significantly impacted by those drivers. The cloud turns a minor application integration need into a significant one.

Another thing to remember is that even applications that didn't require integration when run in-house will require some integration -- and perhaps a lot of it -- in the cloud. There is almost always a need to treat the connection between users and cloud-hosted applications as integrated workflows. So, don't bother to ask whether your cloud use will involve an application integration strategy -- assume it will.

What questions should you ask? Here's a list:

  1. Do you have a realistic, formulated plan for cloud computing adoption? Almost every business thinks they'll use the cloud, but an application integration strategy should be associated with real projects -- not projections.
  2. Does your cloud computing service contain any of the following features:
    1. Elastic IP addresses, such as those provided by Amazon;
    2. Load balancing in any form;
    3. Elastic cloud resource tools, such as Availability Zones;
    4. Cloud-hosted Web services that add data flow processing, caching or work scheduling and queuing; and
    5. Web front-end processes in the cloud, converging on back-end processing in-house.
  3. Do you have, or have you been told to plan for, the use of multiple cloud providers?
  4. Are you truly committed to a hybrid cloud?

If you didn't answer "Yes" to any of the questions above, and if your company has more than 100 employees, you should probably reconsider the questions and your responses. Few companies, other than very small businesses, can escape application integration needs completely. Therefore, even if you're sure you have answered the questions correctly in the negative, pick the driver you had to consider most carefully and consider that to be your application integration driver.

If you answered "Yes" only in one driver category, your integration needs should focus on that specific driver. The more "Yes" responses you had in that single category, the more you should focus on products and practices developed for that driver alone.

If you answered "Yes" to questions distributed across multiple drivers, you should consider yourself to be highly dependent on application integration, and look for products and practices that cover all of the issues of integration.

An application integration strategy involves an ordered movement of work between applications and components. Workflow and component location and registration are both important. How the two issues are balanced best for your needs will depend on how you've answered the questions above.  With your responses in hand, you're ready to move to the process of issuing an RFP for application integration products.

Next Steps

Enterprises can manage applications using Talend ESB and its open source version, Open Studio for ESB.

WSO2 ESB focuses on enterprise mediation and deployment

This was last published in July 2015

PRO+

Content

Find more PRO+ content and other member only offers, here.

Buyer's Guide

Application integration software: A buyer's guide

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

What is your main driver for application integration -- agile, componentization or cloud computing?
Cancel

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide

SearchWinDevelopment

Close