3 ms·
One of the ParadeDB maintainers here -- Being PostgreSQL wire protocol compatible is very different from being built inside Postgres on top of the Postgres page
by philippemnoel 1y ago
One of the ParadeDB maintainers here -- Being PostgreSQL wire protocol compatible is very different from being built inside Postgres on top of the Postgres pages, which is what ParadeDB does. You still need the "T" in ETL, e.g. transforming data from your source into the format of the sink (in your example CrateDB). This is where ETL costs and brittleness come into play.
You can read more about it here: https://www.paradedb.com/blog/block_storage_part_one https://www.paradedb.com/blog/block_storage_part_one
- worldsayshi 1y agoSounds very interesting! Unfortunately AGPL license makes it hard to bring into projects.
- philippemnoel 1y agoHow so? Many popular projects are AGPL. MinIO, Grafana, etc. We wrote about this here: https://www.paradedb.com/blog/agpl https://www.paradedb.com/blog/agpl
- worldsayshi 1y agoSo, I'm not versed enough in legal matters to be certain about this, so I tend to fallback to caution, but (A) customers I've worked with in the past seem to be wary of such copyleft licenses and (B) the contagious nature of such license would make me think twice about using it in a project of my own as well. It would be nice to have such notion challenged but I'm not sure what would change my mind. I would expect that most commercial companies that use Grafana would obtain a commercial license?