Use field mapping to simplify field names for reducing storage volume?

[jsonchou]

Is there a strategy of renaming field keys?

By mapping originally lengthy field keys (such as product_name, product_id, product_url) to shorter identifiers (e.g., a, b, c) during storage, which will reduce data storage overhead.

When reading data, restore the simplified identifiers to their original field names according to the mapping relationship.

Great always start from small details.

[jsonchou]

Explicit mapping or implicit automatic mapping

[kishorenc]

Is there a benefit to doing this within Typesense rather than managing it within your app?

[jsonchou]

Is there a benefit to doing this within Typesense rather than managing it within your app?

So, is it worth actively helping clients reduce their memory usage by 3-5%? From the perspective of software solutions, this is also a question worthy of long-term consideration.

Based on my personal experience, I often employ this approach for data optimization, such as data reduction and network transmission. So, can similar optimization strategies be applied to Typesense data storage? (i really dont know how the typesense data be storaged.)