Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Understanding Hybrid Integration Platforms

DZone's Guide to

Understanding Hybrid Integration Platforms

In this post, we discuss some best practices around Hybrid Integration Platforms, and what development teams are using them to achieve.

· Integration Zone ·
Free Resource
CRM integration has become the cornerstone to meeting initiatives across organizations. Explore the top 6 value-driven Salesforce CRM integrations ebook.  

Based on the research of researchandmarkets.com, the market cap for Hybrid Integration Platforms (HIP) will grow from $17.14B in 2017 to $33.6B in 2022. This shows the importance of the Hybrid Integration Platforms and their relevance to enterprises. First of all, it is essential to understand the concept. The term “Hybrid” means a combination of more than one entity (most of the time 2). I drive a hybrid Toyota vehicle which runs on electricity (battery) as well as fuel (petrol). In the world of integration, hybrid means integrating systems which reside both on-premise and in the cloud.

When it comes to “on-premise” systems, they can be running on physical hardware, virtual machines, containers, or in a virtual private cloud. The meaning of an on-premise system in the world of integration is that the user has control over application maintenance.

“Cloud” systems means the systems which are running on a public cloud which runs at the vendor's own data centers (or public IaaS clouds such as EC2, Azure, or GCloud) and fully managed by the vendor. Sometimes users may get some admin privileges, but, most of the time, it's the vendor who maintains of the system.

The term Hybrid Integration Platform means a platform which can interconnect both on-premise and cloud-based systems. Even though we differentiate the systems based on their installed location and the maintenance capabilities, all the systems communicate with the integration platform using 2 main principals:

  • Communication (Transport) protocol (e.g. HTTP, JMS, TCP, IDOC, etc.)
  • Content Type (message format) (e.g. XML, JSON, Binary, Text, etc.)

From the Integration Platform’s perspective, what matters is to understand the transport protocol and the message formats. In most of the well-known integration platforms, these are handled through:

  • Protocol Connectors - to deal with communication protocols (HTTP, JMS, TCP, etc).
  • Message Builder/Formatter - to deal with message formats (XML, JSON, Binary, etc).

With the use of the two above-mentioned components, an Integration Platform can interface with any system and integrate with other systems using a canonical internal message representation (or not). Some platforms keep a canonical representation while others perform the transformations as necessary.

On top of these standard protocol connectors, some integration platforms have build-specific connectors for cloud APIs like Salesforce, Twitter, Gmail, Facebook, etc., so that integration with those systems are abstracted and make it easier for the developers. These Cloud Connectors are one of the key factors when selecting a proper Hybrid Integration Platform. Some vendors offer these connectors for free while others offer these connectors at a cost.

Another important aspect of a HIP is the ability to extend their core functionalities through simple and well-defined interfaces. When it comes to integration, there can be so many on-premise systems which have been written with proprietary standards (especially Commercial Off the Shelf (COTS) systems) and it is really important that HIP can extend its capabilities and deal with these kinds of systems.

Another aspect of a HIP is the deployment flexibility. The platform must be able to deploy on-premise as well as in the cloud. It would also be a value addition if that is available as a public cloud offering.

If a particular Integration Platform or a product offers the above-mentioned capabilities, we can consider that as a good candidate for your Hybrid Integration Platform requirement.

On top of these technical capabilities, another key factor in identifying a good HIP is the user experience when it comes to integrating multiple systems. The concept of Citizen Integrator has become a key factor in selecting a good HIP. The term Citizen Integrator has many different meanings. But the high-level idea is that a person who understands the business value of systems and their interconnections will become a citizen integrator if he is willing to learn about the usage of the technology without going into enough detail to write code. Due to this factor, most of the vendors are building visual tools to help Citizen Integrators to easily achieve their targets without worrying about writing code.

In addition to the above-mentioned capabilities, having the following features would add icing to the cake.

  • Analytics capabilities.
  • API management capabilities.
  • Identity and Access Management capabilities.

Sync, automate, and notify lead to customer changes across marketing, CRM, and messaging apps in real-time with the Cloud Elements eventing framework. Learn more.

Topics:
integration ,cloud integration ,hybrid integration ,integration platforms

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}