Pragmatic Approach to Application Integration

Cedric Monier, Director, Integration Corporate Program — Product & Solution Marketing, Axway

“The difference between the two technologies — enterprise service and file-based application integration — is more in the data exchange layer and the architecture of the core runtime components. When you manage files, you’re looking at managing very high volumes of data in a very efficient…very reliable way, and with very little complexity. This requires very specifically designed solutions.”

All Development is a High-Level Integration Activity

John Thielens, Chief Architect, Cloud Services, Axway

“The maturity of component architectures, event-driven design, workflow as a development methodology, the availability of true, service-oriented components…means that all development is really a fairly high-level
integration activity.”

File-Based Integration: Faster, More Cost-Effective

Cedric Monier, Director, Integration Corporate Program — Product & Solution Marketing, Axway

“Most solutions on the market require (that you) modify the application so that they speak, rather than through files, through messages, to an ESB or to an integration suite.  And therefore, rather than using the existing files, you just have to re-engineer your applications so they are able to generate messages so that the integration task can be handled by the solution you put in place. So having an integration suite that matches the managed files allows you to implement integration services much faster, because you don’t have to re-arrange any of the applications, and very broadly in your information system.”

  • Calendar

    • September 2018
      M T W T F S S
      « Feb    
       12
      3456789
      10111213141516
      17181920212223
      24252627282930
  • Search