←back to thread

Show HN: Marmot – Single-binary data catalog (no Kafka, no Elasticsearch)

(github.com)
102 points charlie-haley | 1 comments | 02 Dec 25 14:59 UTC | HN request time: 0s | source
Show context
paddy_m ◴[02 Dec 25 15:36 UTC] No.46122258[source]▶
When should you reach for a data catalog via a data warehouse or data lake? If you are choosing a data catalog this is probably obvious to you, if you just happened on this HN post less so.

Also, what key decisions do other data catalogs make via your choices? What led to those decisions and what is the benefit to users?

replies(1): >>46122431 #
1. charlie-haley ◴[02 Dec 25 15:49 UTC] No.46122431[source]▶
It depends on your ecosystem. If everything lives under one vendor their native catalog will probably work really well for you. But most of the time (especially for older orgs) there's usually a huge fragmented ecosystem of data assets that aren't easily discoverable and spread across multiple teams and vendors.

I like to think of Marmot as more of "operational" catalog with more of a focus on usability for individual contributors and not just data engineers. The key focus being on simplicity, in terms of both deployments and usability.