Now, the /{tenant}/{client}/data/{type} endpoint returns data with chunked transfer encoding.
What does this mean?
Using chunked transfer encoding, the service does not wait to get all the queried data from a database, but responds by transferring data in segments. This improvement helps the Document service manage its memory more efficiently.
Example: Previously, if you queried 100 documents with the /{tenant}/{client}/data/{type} endpoint, the Document service waited until the database returned all 100 documents and stored them in internal memory. Next, the Document service returned a full response. If you multiply this behavior by the number of tenants, the process can use a lot of memory.
In the improved flow, the service sends documents that the database returns in response chunks, without waiting for all of the documents.
For more information, see Chunked transfer encoding.
Impact of this improvement
You do not need to change anything. All REST clients supporting HTTP/1.1 can use chunked transfer encoding by design.
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.