Timeline for Move from mft to api REST style to get or post large data 200mb , is it best practice?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2021 at 9:24 | comment | added | Hans-Martin Mosner | I'm not an expert and I can't speak for experts, but I suspect that pagination is recommended for list-like data intended to be displayed to a user who might only want to scroll through the first 1-4 pages of data. It allows you to present first results quicky and avoid transferring too much unnecessary data. In your case, the whole data is always needed, and it is prepared ahead of time, so there's no huge delay before data becomes available. | |
| Jun 3, 2021 at 9:18 | comment | added | Benhassine Mohamed | thanks @Hans-Martin , the correct flow data is : PARTNER==> MFT ==> MY CLIENT , the client will expose GET API ( exposed by APIGEE) to expose 200MB of txt data and my client will invoke This HTTP GET , How we can get the file in a single GET request with compression without pagination ? if so why all experts recommand pagination to get huge Data from API REST ? Thanks | |
| Jun 3, 2021 at 9:11 | comment | added | Benhassine Mohamed | Thanks @Hans-Martin , the correct flow data is :Client <==> MFT <==> Partner | |
| Jun 3, 2021 at 9:05 | history | answered | Hans-Martin Mosner | CC BY-SA 4.0 |