Live data from Hacker News

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

github.com

11–20 of 24 posts

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

#11
post #9
post #6

Hey there, Great to see Marmot here and I'm a huge fan of your project. Recently, we deployed a catalog but we went with open-metadata https://open-metadata.org/ another amazing project. What we missed on marmot was existing integrations with Airflow and other plugins like Tableau, PowerBI etc as well as other features such as sso, mcp etc. We're an enterprise and needed a more mature product. Fingers crossed marmot…

That's useful feedback. Charlie, what's the process for adding integrations? A tutorial would be great. The plugin links here don't work: https://marmotdata.io/docs/Plugins/

Hey, there's some documentation around creating plugins here. It's relatively simple and involves adding a new Go package to the repo. Currently they have to be compiled into the Binary but I'd like to support external plugins at some point https://marmotdata.io/docs/Develop/creating-plugins

Also, thanks for pointing out the issue with the docs, I'll get that fixed!

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

#12

Hey HN, I wanted to show off my project Marmot! I decided to build Marmot after discovering a lot of data catalogs can be complex and require many external dependencies such as Kafka, Elasticsearch or an external orchestrator like Airflow. Marmot is a single Go binary backed by Postgres. That's it! It already supports: Full-text search across tables, topics, queues, buckets, APIs Glossary and asset to term associatio…

How does this get the maps of the data flows and so on? Does it require read credentials to each data silo, or is there a manual mapping process?

It supports either, I didn't want to restrict people to just one method of getting their catalog populated. The CLI and Plugin system works on needing read credentials to a given Service, it then populates the catalog with those assets. Any lineage links currently need to be done manually (unless they're part of the same plugin). Otherwise, you can integrate with your existing IaC pipelines using Terraform or Pulumi to populate the catalog at deploy time instead of needing to scrape a bunch of services.

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

#13
post #6

Hey there, Great to see Marmot here and I'm a huge fan of your project. Recently, we deployed a catalog but we went with open-metadata https://open-metadata.org/ another amazing project. What we missed on marmot was existing integrations with Airflow and other plugins like Tableau, PowerBI etc as well as other features such as sso, mcp etc. We're an enterprise and needed a more mature product. Fingers crossed marmot…

[dead]

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

#16
post #15

How are you able to see a datasets lineage across storage types. For example how are you able to see that an s3 buckets files are the ancestor of some table in Postgres?

Oh I see it uses open lineage. I thought it was able to handle discovery

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

#17
post #16
post #15

How are you able to see a datasets lineage across storage types. For example how are you able to see that an s3 buckets files are the ancestor of some table in Postgres?

Oh I see it uses open lineage. I thought it was able to handle discovery

It can handle discovery within a plugin if the asset types are related. You can also manually add lineage via the UI or use Terraform to create lineage links via IaC. It's pretty complicated to automatically handle discovery of asset lineage, I'm yet to find a nice way of doing it that can work for many use-cases

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

#18
Not to be confused with Marmot, the multi-master distributed SQLite server, which has been around for a couple years longer and just came out of 2 years in hibernation, shed its NATS/Raft fat in favour of a native gossip protocol for replication.

https://github.com/maxpert/marmot

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

#19
I’ve been burned by metadata platforms twice now and honestly, it’s exhausting.

The demo is always incredible - finally, we’ll know where our data lives! No more asking “hey does anyone know which table has the real customer data?” in Slack at 3pm.

Then reality hits.

Week 1 looks great. Week 8, you search “customer data” and get back 47 tables with brilliant names like `customers_final_v3` and `cust_data_new`. Zero descriptions because nobody has time to write them.

You try enforcing it. Developers are already swamped and now you’re asking them to stop and document every column? They either write useless stuff like “customer table contains customers” or they just… don’t. Can’t really blame them.

Three months in, half the docs are outdated.

I don’t know. Maybe it’s a maturity thing? Or maybe we’re all just pretending we’re organized enough for these tools when we’re really not.

Post reply on HN