TrailDB is optimized for a very specific data model (http://traildb.io/docs/technical_overview/#data-model http://traildb.io/docs/technical_overview/#data-model

TrailDB is optimized for a very specific data model (http://traildb.io/docs/technical_overview/#data-model http://traildb.io/docs/technical_overview/#data-model) which allows it to do compression that you couldn't do with other data layouts. TrailDB is a C library, Parquet and Avro are not. Depending on your use case this might be a pro or a con.