SEE (Semantic Entropy Encoding) is a schema-aware JSON compression format.
It keeps JSON searchable while compressed, cutting I/O and CPU cost.
Benchmarks: ~19.5% of raw size, lookup p50 ≈ 0.18 ms.
Curious about your thoughts — especially from those using Zstd or Parquet in production.
What would be your biggest blocker for adopting schema-aware compression?
SEE (Semantic Entropy Encoding) is a schema-aware JSON compression format. It keeps JSON searchable while compressed, cutting I/O and CPU cost. Benchmarks: ~19.5% of raw size, lookup p50 ≈ 0.18 ms.
Article: https://medium.com/@tetsutetsu11/the-hidden-cloud-tax-and-th...
Slides: https://speakerdeck.com/tetsu05/see-the-hidden-cloud-tax-bre...
GitHub: https://github.com/kodomonocch1/see_proto
Curious about your thoughts — especially from those using Zstd or Parquet in production. What would be your biggest blocker for adopting schema-aware compression?