Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace API Connect
Created by Guest
Created on Dec 16, 2024

API Gateway of API Connect should support flow control for large Payloads (request/response)

The API Gateway of API Connect should support flow control for large Payloads in API Requests and API Responses.

API Gateway should manage the transmission rates when the server or client cannot receive requests fast enough. In this cases API Gateway should limits the amount of data that is received from the slower communication partner, for not having to buffer data on the gateway.

As flow control is missing, we had cases with large response paylods and slow client connecitons, where the API Gateway went into an out-of-memory and reloaded (which causes all traffic on that particular gateway to terminate)

As multiprotocl gateway in DataPower so support flow control, we are wondering why this is not the case in API Gateways.

Idea priority Urgent