Cloud-Based Integrations vs. On-Premise Models

This is an article from DZone's 2022 Enterprise Application Integration Trend Report.

For more:


Read the Report

For large enterprises, where integration with different platforms is important for various business activities, enterprise integration is the most popular term for the integration architecture. Enterprise integration has evolved a lot from traditional batch processing using ETL (extract, transform, and load), where data feeds from sources were used for business processing/ transformation and loading to the target data source. 

Going Cloud-Native with David Linthicum

Cloud computing has come a long, long way from the early days of mainframe timesharing technology and virtualization. Over the past decade alone, we’ve seen cloud computing experience tremendous growth, providing ubiquitous solutions for both consumers and enterprises. This trend is expected to continue with the rise of cloud-based services for machine learning, artificial intelligence, and edge computing.

However, the transformation to cloud computing remains a very challenging prospect for many enterprises. Enterprises need to consider factors such as cost, security, legacy and on-premise technologies, and the value of using cloud-native vs cloud-agnostic services.

How NOT to Be API-Misled for Connectivity!

How NOT to be API-misled for connectivity!

It was a few years back when API-led connectivity was getting popular and our customers wanted to see it being brought into practice. Some of them also began to choose their hybrid integration products based on the product’s inherent support for the approach. After having implemented two large hybrid integration programs for two different industries (Banking and Manufacturing), I thought I should share my experience as do’s and don’ts for API-led connectivity and Hybrid Integration.

API-led connectivity

The approach was termed as the next step in the evolution of SOA, which is why its principles and the very fundamental concepts will remain timeless, at least in the context of software architecture.

Why API Schemas Are Better Than Connectors for Integration

Why Enterprise Application Integration Platforms Have Traditionally Used Connectors

A connector (often called an SDK) is a piece of code that wraps an external API so that it can communicate with your application. Huh? Ok, well, let’s run through a practical example.

Say you wanted to update a contact in your CRM system every time there was a change to the same contact in your ERP (or accounting system). The providers of both the CRM and ERP system document their APIs on their websites. This documentation describes all of the operations available in the API, the method by which you should connect to the API, security, and other settings.