Legacy architecture meets new cloud applications
Published on 16 August 16
Simon0
In today's cloud based world there are unlimited amount of cloud apps available however in many cases this creates an integration challenge with legacy systems.
In the past there have been various options for integration ranging from middle-ware, individual plugins, ETL tools and if the company can afford it an ESB (Enterprise Service Bus). Over the years many developers have struggled to find a happy medium with price, ease of use and of course minimize the ongoing maintenance of your architecture.
“"The main reason why developers are not integrating systems is due to prohibitive costs and the time it takes to deploy and maintain" noted Simon Church DSYNC”
We set out to ask developers what was stopping developers from joining disparate systems together and found the following results
1) It is too cost prohibitive to use some of the IPAAS providers available
2) The IPAAS providers limit the amount of connectors you are allowed to use
3) It is difficult to visualize and see the data flows when integrating
4 The products available were point to point products and were coded from one to another not allowing flexibility and scale
5) The time to integrate was excessive and potentially takes the production environment offline.
6) The products that transform the attributes were too expensive to deploy
Based on the above survey of our fellow developer community we began to build an affordable IPAAS system for developers.
Integration of systems can lead to better efficiency within organisations. When organisations have up to date transaction data applied across their networks it leads to better visibility and the ability to make real time decisions.
This blog is listed under
Development & Implementations
and Enterprise Applications
Community
Related Posts:
Post a Comment
