Building a robust integration architecture requires a clear understanding of the core components involved. Before you jump into choosing specific tools or platforms, it’s crucial to understand the fundamental concepts of APIs, Integrations and Connectors.
Let’s break down these key concepts:
- APIs are interfaces that define how different software systems interact in a standard protocol (HTTP, gRPC, GraphQL..). They expose specific functionalities of an application, allowing other systems to access and utilize those functionalities without needing to understand the internal complexity. APIs are essential for building loosely coupled, interoperable systems.
- Integrations are tools and services for transforming systems interactions to match the contracts of each application. More than a simple format translation, those interactions are often structured in workflows orchestrated by an Integration platform. Integrations are essential for building end to end user experiences in a fast and robust way.
- Connectors are pre-built reusable bridges, handling the underlying communication protocols, security and data formats so you don’t have to write custom code to interact with systems. They also provide an alternative for platforms that don’t expose APIs. Connectors are crucial for accelerating development and reducing complexity.
Google Cloud offers customers a global platform to help them build digital experiences. It includes 3 key services to build robust architectures : Apigee, Application Integration and Integration Connectors
- Apigee - the API Manager - to expose, publish, secure and monetise APIs
- Application Integration - the iPaaS - to build simple and complex transformations & workflows in no/low code
- Integration Connectors - the connectors service - to connect to 150 platforms (2024) of your IT system
A common question I hear is: 'Where does Application Integration fit in my API strategy? When do I need an API Manager alongside it?’
This article addresses common questions about Application Integration’s API interaction capabilities and clarifies its role in conjunction with an API Manager like Apigee.
The synergy of Application Integration, Apigee and Integration Connectors
Considering the following reference diagram illustrating how those services work together:
Assuming that you are using HTTP as your APIs standard protocol, Apigee communicates with other systems using HTTP requests/responses. API Products define a clear contract for application developers through API specifications. Apigee’s role is to make sure that the response from the backend (Application Integration in our case) is matching this specification and hiding any complexity or internal messages that do not meet the developer needs, defined in the contract.
Application Integration uses messages to connect various systems. During an Integration flow the input messages become variables that can be processed and transformed, enriched or merged with lookups from other applications via connectors or REST, along with new variables that will be created. At the end of the Integration flow, those variables will define the response, which can be an enriched message.
Common Questions & Clarifications
-
Q: I want to run an integration on Application Integration via API with methods other than POST. How can I do that?
-
A: Application Integration itself doesn’t inherently handle different HTTP methods like GET, PUT, or DELETE. It focuses on processing data through a series of processing steps which often includes interactions with other data sources or applications. To achieve RESTful interactions with Application Integration, you’ll need an API Manager like Apigee. Apigee acts as an intermediary, converting HTTP requests into variables that Application Integration can understand, and then transforming Application Integration’s output back into standard HTTP responses.
-
Q: I need to update HTTP headers in the API call response from Application Integration.
-
A: Again, this is where an API Manager shines. Application Integration doesn’t directly manage incoming HTTP headers. Apigee allows you to intercept responses from Application Integration and modify headers as needed. This gives you fine-grained control over the API’s behavior and presentation.
-
Q: The API response from Application Integration contains more fields than expected (system logs and error messages).
-
A: This can happen when Application Integration’s output includes debugging or system-level information not meant for external consumption. An API Manager like Apigee helps you filter and shape the response, ensuring that only the necessary data is returned to the API consumer.
Tip: Standardize API interfaces for your consumers with Apigee Shared Flows. Define the necessary transformations once and apply them to all proxies interacting with Application Integration.
Why Application Integration Isn’t Just About HTTP ?
Application Integration’s strength lies in its versatility. While it can integrate with APIs, it’s not limited to them. It can also be triggered by events, scheduled tasks, and real-time data changes (CDC). This makes it a comprehensive platform for a wide range of integration scenarios beyond simple API interactions.
Application Integration and Apigee are complementary tools. Application Integration excels at handling the logic and data transformation within your integrations, while Apigee provides the API management layer, ensuring your integrations are accessible and consumable through standard API protocols. By combining these powerful services, you can unlock the full potential of Google Cloud’s integration capabilities.
Have fun and let me know if you have any questions!