The vendor route feels great at the beginning with clean UX and fewer moving parts, until costs creep up or you suddenly need an engine or table format the platform doesn’t really support.
The open route gives you freedom, but then you’re managing multiple catalogs, inconsistent metadata models, and a bunch of glue code nobody planned for but still ends up living forever.
Gravitino seems to be tackling the “one catalog vs many catalogs” issue.
Where do lineage and ACLs actually live in your setup? I’m genuinely curious how people are handling this today.
Comments
I’ve seen teams struggle on both sides of this.
The vendor route feels great at the beginning with clean UX and fewer moving parts, until costs creep up or you suddenly need an engine or table format the platform doesn’t really support.
The open route gives you freedom, but then you’re managing multiple catalogs, inconsistent metadata models, and a bunch of glue code nobody planned for but still ends up living forever. Gravitino seems to be tackling the “one catalog vs many catalogs” issue.
Where do lineage and ACLs actually live in your setup? I’m genuinely curious how people are handling this today.