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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Thank you. We understand that the main use case here is to manage REST APIs with large payload (multiple giga bytes.), like file transfer/upload/download APIs. We agree that enhancing streaming capabilities would provide an improved adoption for REST APIs with large payload. Status of the idea is updated to Future Consideration. Given this, it would be good to have feedback/votes from other readers on the use case presented here. What kind of processing is required beyond pass-thru scenarios? Is there any upper limit? We will continue to monitor.
I am afraid but I cannot share a sample api definition, for the time being, we do block customers from publishing APIs with large payloads. You can take any REST API that e.g. returns a large payload in the response or returns a pdf document. Large in our case means up to multiple giga bytes.
From a conversation with the gateway developement team we got the following messages:
For streaming mode, there is no memory used by the policy, there is no modified request and no modified response so the rule of thumb for "worst case" estimation is 2x payload size. This 2x assumes the request and response are same size which is often a bad assumption.
Steaming was not designed to conserve memory it was designed to conserve latency and that has a beneficial side effect of reducing memory.
So we are looking for a solution that allows us to "stream large API payloads" via DP API gateway, the same way any http-proxy would do. So streaming capabilities should be improved to also optimize memory utilization on the gateways
Apologies for the length of time this idea has been in the review status. In API Gateway with streaming we aim to reduce the memory footprint.
In streaming mode, the API Gateway passes message payloads through without parsing and the API Gateway does not buffer the entire payload of a message into the memory. However this can only occur in limited situations as documented and highly dependent on the process.
https://www.ibm.com/docs/en/datapower-gateway/10.0.1?topic=gateway-streaming-api-payload
Would you be willing to open a support case and share your sample API via support case to be triaged?
In the IDEA FAQ i found the following statement:
How quickly will I hear back from IBM once I’ve submitted an idea?We try to get back to all submissions within 30 days and our goal is to give you a decision within 90 days. The product management team may contact you to ask for additional information or feedback as we refine your idea.
So what is the current status of my IDEA, which I created 2 month ago?