Changes to HttpService:JSONEncode and HttpService:JSONDecode

[Gratka0414 (Gratka)]

This may be a little unrelated:
Currently when saving a very big table to a Datastore/Memorystore, I first encode it to JSON with HTTPService, then turn it into a buffer with buffer.fromstring(), and then compress using EncodingService:CompressBuffer().
But I’ve read that Roblox compresses data automatically.
So if I want to make my tables take as little space as possible, is my method good? Or is it all unnecessary because Roblox compresses tables themselves? Or, maybe it only applies to strings or buffers, and I don’t have to compress it only after I turn it into a table/string?

(I’m basing this question on those posts, but that was locked and I wanted to ask a staff member:)

@technology1111

The result of JSONEncode on the buffer is used. Roblox uses zstd (sometimes) and base64 (always) to represent the data as json. The json is then counted against the data size limit

@WheretIB

Buffer data is still being compressed, so the absolute maximum buffer size that can be stored is 50MB, but only if it can be compressed below 3MB by the engine.