Apigee Edge Transfer limits

danielhoenig
Participant III

Does anyone know what the following transfer limits are for Apigee Edge? We need to send large amounts of data and need to know when to break it into chunks so we don't gets errors from our Apigee proxies.

  1. Max transfer size, with streaming enabled.
  2. Transfer timeout with streaming enabled.
Solved Solved
0 1 471
1 ACCEPTED SOLUTION

1) In theory, there is no maximum size, per the limits doc: https://docs.apigee.com/api-platform/reference/endpoint-properties-reference but obviously any connectivity issues would require you to re-start the transfer from scratch, which isn't ideal.

2) There is no transfer timeout per-se, but there are IO timeouts on the MP (see https://docs.apigee.com/api-platform/reference/endpoint-properties-reference) and router (https://docs.apigee.com/api-platform/fundamentals/virtual-host-property-reference?hl=en) as well as buffering configuration on the router that you'd need to look at.

I'd argue that the suggested size to split up the payload depends a lot on the quality of the networks you expect your API callers to be using. If they have super reliable connectivity (eg, datacenter with redundant internet connections) relatively large (eg, 100MB) chunks should be no problem. If they're on unreliable 3g mobile connections (eg, remote sites) then even 10MB might be too large.

View solution in original post

1 REPLY 1

1) In theory, there is no maximum size, per the limits doc: https://docs.apigee.com/api-platform/reference/endpoint-properties-reference but obviously any connectivity issues would require you to re-start the transfer from scratch, which isn't ideal.

2) There is no transfer timeout per-se, but there are IO timeouts on the MP (see https://docs.apigee.com/api-platform/reference/endpoint-properties-reference) and router (https://docs.apigee.com/api-platform/fundamentals/virtual-host-property-reference?hl=en) as well as buffering configuration on the router that you'd need to look at.

I'd argue that the suggested size to split up the payload depends a lot on the quality of the networks you expect your API callers to be using. If they have super reliable connectivity (eg, datacenter with redundant internet connections) relatively large (eg, 100MB) chunks should be no problem. If they're on unreliable 3g mobile connections (eg, remote sites) then even 10MB might be too large.