Evaluate and add brotli

[ManjotS]

https://certsimple.com/blog/nginx-brotli

[bogas04]

In my own research, brotli is great (20% compression improvement over gzip), however its compression time is pathetic, and is meant to be compiled before hand as opposed to compressing on the fly. If we can support that, then we should definitely go for it, as all modern browsers support it.

I can setup our build process to also produce .br files, which can then be sent to CDN, and nginx can be updated to serve it (brotli-static)

[ManjotS]

this pretty low priority, especially if you aren't confident in it.

[bogas04]

@navdeepsinghkhalsa What can we do to make this happen? We can produce brotli JS assets at build step (webpack plugin) to begin with.

[navdeepsinghkhalsa]

@bogas04 That's great that you are ready for this at the front-end. Just need to evaluate if it's something we want to do. I will take a look after this sprint closes.

[bogas04]

20% better compression at no cost. Just that we need to pre-build the files.

[saintsoldierx]

@navdeepsinghkhalsa do we still want to do this? please re-assign as needed.

[saintsoldierx]

This ticket still valid @ManjotS

[ManjotS]

@tsingh777 please let us know

[saintsoldierx]

@tsingh777

[saintsoldierx]

ping @tsingh777

[tsingh777]

Would like to see if expressjs/compression#172 gets accepted. keep it open at low priority.

[gurjit03]

This needs more discussion/research and might be even avoidable if we opt for next.js or any other framework.