Apigee Integration system limits

You're viewing Apigee X documentation.
View Apigee Edge documentation.

This section describes Apigee Integration system configuration limits you should consider as you design, build, and manage your integrations. The Apigee Integration feature is designed for stability and performance when configured for use cases within these system limits.

Data processing

Apigee Integration is not recommended for use cases that require the movement of bulk data or focus on extract, transform, and load (ETL) processes.

Similarly, we do not recommend using Apigee Integration to process data that is greater than 10 MB if you want access to execution logs, retry functionality, and monitoring. If input payloads exceed 10 MB, Apigee Integration switches to a default "no-persistence" mode that renders these features unavailable.

System timeouts

The following system timeouts apply:

  • For synchronous execution of integrations, the timeout is 2 minutes.
  • For asynchronous execution of integrations, the timeout is 50 minutes.

Apigee Integration is not recommended for executions with an anticipated run time exceeding these timeouts.

System consistency

Apigee Integration is a distributed system that provides "eventual consistency." It uses caches throughout the system that may take up to 10 minutes to clear and refresh.

This means that it may take up to 10 minutes for a published integration to incorporate and run a new version of the integration. For example, when used in a high-frequency scenario (such as integrations using the For Each Parallel task or Cloud Pub Sub tasks and triggers) you should consider that older versions of the integration may run for up to 10 min after a new version is published.

Integration limits

You can have maximum of 100 tasks in an integration. If there is a need for more than 100 tasks, it is recommended that you split your integration into multiple integrations.

Trigger limits

In addition to the above system limits, there are some trigger-specific recommendations to consider as you design, build, and manage your integrations. The limitations are detailed in the reference page for each trigger shown below:

Task limits

In addition to the above system limits, there are some task-specific recommendations to consider as you design, build, and manage your integrations. The limitations are detailed in the reference page for each task shown below:

Supported regions

Apigee Integration supports data plane and runtime regionalization. During the integration creation process, users can select the specific region for data and execution to reside.

Apigee Integration supports the following regions:

  • all us regions
  • northamerica-northeast1
  • europe-west2
  • asia-southeast1
  • asia-south1
  • australia-southeast1