With more mission-critical applications such as CRMs and ERPs moving to the Cloud, the integration landscape is changing. But what’s the degree of change? Is it really changing that much or have the mediations (services that connect the internal and external processes) simply changed to support different data packaging, communication protocols and activation methods while continuing to perform the same functionality? If your integration toolset can’t adapt to these changes, you’ll have to rebuild your integrations.
Let’s consider current real-world use cases: integration using a premise-to-Cloud implementation and integration within the Cloud such as Cloud-to-on-premise or Cloud-to-Cloud. Even though the endpoints are different and cross system boundaries, the base mediation involved is simple: Continue reading
Last week, I was interviewed by Alex Woodie of IT Jungle, for his Four Hundred Stuff column. The primary focus of Alex’s column was on the trajectory of Cloud computing adoption and the challenges that companies face as they add Cloud integration to existing EDI, application, and data integration practices. I encourage you to click through and read Alex’s article, but in this post, I want to focus on the evolutionary path that is taking us from traditional EDI to Cloud integration.
For most companies, EDI remains the single most important B2B integration requirement. And new characteristics that reflect the way “EDI” is practiced today make it more relevant and important than ever. Fifteen years ago, EDI was almost exclusively batch-oriented, enabled by VANs, and focused on translation between flat files and X12 or EDIFACT standard EDI documents. Since then, EDI has changed in several important ways: Continue reading