Hybrid Integration & Ground-to-Cloud Patterns We're Seeing in the Wild

By Brian Busch in Enterprise Integration Posted Jul 22, 2020

Hybrid integration isn’t just a strategy anymore - it’s something you can buy.

And more and more enterprises are thinking about integration investments through the lens of a HIP. But the challenge is integrating the existing tech stack: I suppose you could buy a new, full HIP, but would you really want to all-at-once migrate and deprecate the existing integrations and tooling?

enterprise ground-to-cloud trends

With the hundreds (or even thousands) of existing apps you use to conduct business, making sure that, for example, your on-prem and cloud-based apps can seamlessly transfer data back-and-forth is critical to eliminating silos and creating efficient processes.

In a recent post on DZone, I go deeper into two of the main patterns that we at Cloud Elements consistently see for enterprises’ ground-to-cloud integration:

  1. Orchestrate from the ESB - For ESBs with secure methods to call out from the on-prem environment, developers can simply call the connector of the cloud service instance.
  2. Create a Reusable API Connector for APIs you own - This method is more common for integrations dealing with custom apps, but involves creating/publishing a public API for your app along with a private Element (a feature-loaded connector built on the Cloud Elements platform) to that API.

Some of the use cases we see that incorporate these patterns include: legacy systems modernization/best-of-breed app adoption (i.e., the HR department adopting Workday), growing e-commerce portfolios, data replication for big data & ML, hyperscaler adoption/deployment, and good ol’ process modernization or automation (i.e. adopting Tipalti for AP automation). 

Want to go deeper into these patterns or curious where API integration fits in a HIP? Check out our solution brief and Point-of-View for all things ground-to-cloud API integration.

Get the brief

Read the POV