One thing though: It would be great if you could include the names of the tools/companies you've included not just the logos. Or maybe put a link on the respective logo.
Most of them are big/common enough to know but there were a few I had to look up via Google's reverse image search. :D
I think what was apparent is how you see the core position of DBT cloud (proprietary SaaS product) as a centre of gravity (Metadata API, etc.). This is something that is not necessary - as long as the format is standardized, any tool could host a metadata layer, or it could be directly stored in the orchestration engine as artifacts (so DBT run can be operated by any agent(s))
Furthermore a unified metadata serving layer could be a job job of data governance/(meta)data exploration tools, such as Marquez, Amundzen etc.
Really interesting article!
One thing though: It would be great if you could include the names of the tools/companies you've included not just the logos. Or maybe put a link on the respective logo.
Most of them are big/common enough to know but there were a few I had to look up via Google's reverse image search. :D
Interesting article.
I think what was apparent is how you see the core position of DBT cloud (proprietary SaaS product) as a centre of gravity (Metadata API, etc.). This is something that is not necessary - as long as the format is standardized, any tool could host a metadata layer, or it could be directly stored in the orchestration engine as artifacts (so DBT run can be operated by any agent(s))
Furthermore a unified metadata serving layer could be a job job of data governance/(meta)data exploration tools, such as Marquez, Amundzen etc.