I have an usecase to download the records to excel. I am following the json-api spec and serializing all the records to json-api data. However I am experiencing serious performance issues since UI has to parse the json-api data for all the thousand’s of records and create the attachment (Excel/CSV).
I have another option of creating the attachment at server side and share the BASE 64 encoded bytes back to UI, which UI can easily transform to attachment.
Do we have any standards as per JSON API spec to follow for downloading the attachments. Please suggest