With an increase in the number of SaaS applications, there is a corresponding increase in the demand for integration projects. Traditional integration teams are struggling to keep up with project demand and might be seen as bottlenecks for the implementation of applications designed by business teams. High-priority backlogs make departmental-based integration time-to-delivery unacceptable to the business.
With this trend, you must consider what approaches you will take to meet the demands for integration projects, even while keeping investment costs down in integration development resources.
You might consider these approaches:
Offer self-service integration
Given the constraints of traditional IT, one option is to think of IT’s role in integration as a service provider, giving different departments the ability to do the integration work themselves. This approach requires that IT establish common architectures, services, access, and tools for integration projects, and then makes these available for use by departmental users. With this approach, IT ensures that the company is protected from potentially disruptive problems that arise from non-experienced users and a mish mash of tools.
Increase asset re-use
One of the best ways to keep up with integration project demand is to limit the amount of new work that needs to be done. And the simplest way to do this is to leverage your existing integration assets such as services, mappings, transformations and orchestrations.
One danger in adopting multiple integration solutions for traditional IT integration projects and departmental integration projects is the creation of silos of integration assets. Customers who have historically adopted best practices around service reuse, such as companies that have Service-Oriented Architecture (SOA) initiatives, are often well positioned to avoid redundant integration work. But, even if you do not have an SOA practice, you should look to leverage any of the assets you can.As you consider how to keep up with project demand, you should also look at how you can provide more flexibility for different types of integration projects. I will discuss this in my next blog.