Point Solutions Creates new Problems
Integration between systems means that their properties are beeing bridged:
- Various technical connections (HTTP, WS, JMS, FTP, etc.)
- Different data formats (XML, CSV, etc.) and standards (OAGIS, SWIFT, EDIFACT, etc.)
- Different processes (synchronous / asynchronous, events, triggers, timings, etc.)
- Various security (IPSec, HTTPS, WS-Security, tokens, etc.)
- Different error handling (exceptions, rollbacks, transaction management, monitoring, alarms, etc.)
- Different operating models (in-house, cloud, outsourced, etc.)
A "quick fix" between the two systems may seem like a good solution but creates problems in operations with instability, problems to scale and difficult to change because of personal dependencies. Many integrations over time also creates a tough situations for IT departments that need to manage a jumble of solutions where an improvement measure can only be applied to one or two of all integrations.
Solutions with Open Technology and Flexible Operations
A good integration solution meets all basic requirements and also has the properties for extended benefits:
- Tool overview of integrations with status and traceability
- The possibility of an iPaas (integration platform as a service) cloud
- Combined and bridged operation models (InHouse + iPaaS = hybrid)
- Reusable components - technology, documentation, methods
- Solution based on open standards and open source - avoid vendor lockin
- Solution with the ability to support and complete responsibility
Standardized Integration Technologies - Reusable Components
When a single integration solution is configured with proven components, it will reduce the cost of integration with an average of 30% (Forrester, 2011). When the integration goes into operation, the large savings will be in terms of stability and predictability. This provides the opportunity to focus on value-creating functions and satisfied system users, before "plumbing" between systems.
