Consider adding compression

[Siegrift]

See: https://github.com/expressjs/compression/tree/88ba108ccebd131f336b7a0fa310f50bcc982992

Our responses are quite large and are well compressible. This could speed up the request-response time. Note that Signed API will be behind CDN so compression should only work if it's supported by the CDN.

[bbenligiray]

Cool idea

Note that Signed API will be behind CDN so compression should only work if it's supported by the CDN

I don't understand why we care about the CDN if we will compress at the server side

[Siegrift]

I think it needs to support the compression to understand that the response is compressed. For example, if someone asks for non-compressed version.

I don't think this is an issue (compression is standard for a long time) but It would be nice to double check.

[bbenligiray]

Alternatively implement an alternative endpoint that serves the compressed version

[Siegrift]

What I mention here is not entirely accurate. When CDN gets a requests it computes "cache key" for it and looks whether it has something stored for this key. If yes, it sends the response. There are different ways how to create the cache key (often configurable), but AWS only looks at domain name and URL path. However, we can configure caching strictly on the CloudFront layer, without the origin support.

Another point to optimize would be pushing data from Airnode feed to Signed APIs. The problem is that both services are CPU bound and the compression optimizes bandwith, but for the cost of CPU (due to compression/decompression). So I am not keen on the idea.

I think it having CDN compression is kinda nice, especially since there is no code change. Still this doesn't feel worth the effort.