Quick & Lean Integration


Published on

The field of Integration is constantly evolving.

At one end comprehensive Integration/SOA suites are being released by big vendors such as IBM, Oracle, SoftwareAG.

But these Integration/SOA Suites (most of them comprising of 10 different components - each catering to a specific Integration/SOA need) are beyond the reach of many mid-sized businesses.

Thats where two new integration methodologies seem to have emerged in the past one year or so.

I have tried to capture this development in the attached presentation.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Quick & Lean Integration

  1. 1. Oct 2010 Satish Dadha Quick & Lean Integration – For Mid-Sized Organizations
  2. 2. Agenda <ul><li>Growing Need for Integration </li></ul><ul><li>Ways to fulfill Integration Needs </li></ul><ul><li>Integration Needs of Mid-sized Organization </li></ul><ul><li>Game Changers: </li></ul><ul><ul><li>Integration using XML Appliances </li></ul></ul><ul><ul><li>IaaS </li></ul></ul><ul><li>Conclusion </li></ul>
  3. 3. Need for Integration <ul><li>Applications today rarely live in Isolation </li></ul><ul><li>Users expect instant access to all business functions an enterprise can offer regardless of which system the functionality may reside in </li></ul><ul><li>Enterprises today have multiple systems with their own varying data and transport protocols – All these need to interface with each other to deliver business functionality </li></ul>CRM Order Mgmt Inventory Mgmt Payroll Billing ERP I N T E G R A T I O N
  4. 4. Endless Appetite for Connections <ul><li>$10 Billion Integration Market - Gartner </li></ul><ul><li>Costs of procuring and installing integration products from leading vendors too high for mid-sized firms </li></ul><ul><li>Consequently $8 Billion in hand coded throw away integration modules are being built </li></ul>20 % - Packaged Software 80 % Hand Code
  5. 5. Application Integration – Choices <ul><li>Integration mechanisms have evolved over time </li></ul>Message Oriented Middleware Enterprise Application Integration Suite Enterprise Service Bus Websphere MQ, JMS Q – Applications connect to common messaging system and exchange data and invoke behavior via messages Middleware to enable integration of systems and applications across the enterprise. ESB = EAI Capabilities + Conformance to SOA & Web Service standards + Value adds like Business Activity Monitoring, Rules Engine Point 2 Point Connectivity File Transfer, Shared DB, Remote Procedure Invocation
  6. 6. Application Integration – Choices <ul><li>EAI & ESB Tools have wide ranging built in capabilities </li></ul><ul><li>They are designed to integrate dozens to hundreds of applications </li></ul><ul><li>They take care of requirements like: </li></ul><ul><ul><li>Reliable Messaging </li></ul></ul><ul><ul><li>Centralized Policy Management </li></ul></ul><ul><ul><li>Business Activity Monitoring </li></ul></ul><ul><li>Of course all these features come at a premium – Software License costs, Specialist Resources etc </li></ul>
  7. 7. Do Mid-sized Firms need all of this? <ul><li>According to Gartner only 10% of enterprises need all the features of an EAI Solution </li></ul><ul><li>Most mid-sized businesses need to integrate fewer than 10 applications </li></ul><ul><li>Most of all smaller firms need quicker ROI – They cannot afford the overhead and time required for EAI Solutions </li></ul><ul><li>!!!!! Using Vendor EAI solutions for Mid-sized firms may be akin to using Chainsaw to open a letter !!!!! </li></ul>
  8. 8. So what's the solution? <ul><li>Most of the mid-sized firms resort to custom coding to fulfill their integration needs </li></ul><ul><li>Custom coding however has 5 serious shortcomings: </li></ul><ul><ul><li>Monopolizes specialist skills </li></ul></ul><ul><ul><li>Custom code may not be always reusable </li></ul></ul><ul><ul><li>Does not provide visibility into Integration transactions </li></ul></ul><ul><ul><li>Rarely scalable and flexible – Its Brittle </li></ul></ul><ul><ul><li>Finally custom coding turns out to be expensive in the long-run </li></ul></ul>
  9. 9. Game Changers ? <ul><li>As we have seen with the evolution of integration products the needs drive the solution </li></ul><ul><li>Two major developments are taking place to potentially cater to the integration needs of smaller firms: </li></ul><ul><ul><li>Integration as a Service </li></ul></ul><ul><ul><li>Hardware XML Appliances </li></ul></ul><ul><li>These solutions cater to “on-premise”, “cloud to cloud” & “on-premise to cloud (hybrid)” Integration requirements </li></ul>
  10. 10. Integration as a Service <ul><li>IaaS is a concept similar to any other cloud offering </li></ul><ul><li>The vendor here will offer the integration functionality on a subscription basis and the user is relieved of most of the hassles associated with building a conventional integration setup </li></ul><ul><li>This is a concept that has just begun to be recognized as one of the solutions </li></ul><ul><li>It is capable of taking care of Transformation and simple BPM requirements </li></ul><ul><li>It brings along all the advantages of a cloud offering </li></ul>
  11. 11. Hardware XML Appliances <ul><li>XML Appliances primarily marketed as B2B Web Services Gateway </li></ul><ul><li>These are purpose built hardware appliances capable of processing XML at wire speed </li></ul><ul><li>Currently they are also being referred to Hardware ESB/SOA Gateway </li></ul><ul><li>Some prominent products in this space are: </li></ul><ul><ul><li>IBM DataPower </li></ul></ul><ul><ul><li>Cast Iron Systems (Acquired by IBM Recently) </li></ul></ul><ul><ul><li>Forum Sentry </li></ul></ul>
  12. 12. Hardware XML Appliances <ul><li>An illustration of IBM DataPower, being used as an SOA Gateway </li></ul><ul><li>Since these products also support – “Any to Any Transformation”, “Content Based Routing” & “Protocol Mediation (to a certain extent” they can be considered to be used for Integration requirements as well </li></ul>HTTPS
  13. 13. Hardware XML Appliances <ul><li>Pros </li></ul><ul><ul><li>Integrate in days rather than months or years – Very limited coding required (XSL Transformation) </li></ul></ul><ul><ul><li>Very limited specialist programming skills reuqired </li></ul></ul><ul><ul><li>Reduced cost for initial procurement & maintenance as physical servers are not needed </li></ul></ul><ul><ul><li>Some of the vendors also provide “pre-built” integration templates </li></ul></ul><ul><ul><li>Console based setup for operations management </li></ul></ul><ul><ul><li>Very efficient in processing XML including encryption & decryption </li></ul></ul><ul><li>Cons </li></ul><ul><ul><li>Does not cover the entire gamut of integration requirements (Limited Protocol mediation support) </li></ul></ul><ul><ul><li>Limited/No BAM functionality </li></ul></ul>
  14. 14. Conclusion <ul><li>If the integration requirements of a client are fairly straightforward and cost is a major factor for them then we should explore these two new approaches that have emerged </li></ul><ul><li>Cognizant can play a role in meeting customer objectives in a cost efficient manner </li></ul>