Multicorn
metriql
Multicorn | metriql | |
---|---|---|
8 | 7 | |
694 | 284 | |
0.4% | 0.0% | |
0.0 | 1.9 | |
over 1 year ago | about 1 year ago | |
Python | Kotlin | |
PostgreSQL License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Multicorn
- Framework to get email attachments into Data Warehouse
- Multicorn – PostgreSQL extension to make Foreign Data Wrapper development easy
- Supabase Wrappers: A Framework for Building Postgres Foreign Data Wrappers
-
Headless BI: Metric Standardization in Action
GoodData Foreign Data Wrapper is a PostgreSQL foreign data wrapper extension. It is built on top of multicore, and it makes GoodData.CN’s metrics, calculations, and data available in PostgreSQL as tables.
-
Launch HN: Hydra (YC W22) – Query Any Database via Postgres
This is really nice! Congrats!
I once started building as a side project something similar but focused on querying cloud resources (like S3 buckets, ec2s, etc... discovering the biggest file from a bucket was trivial with this). I abandoned the project but someone else built a startup on the same concept - even the name was the same: cloudquery.
I built it using the multicorn [1] postgres extension and it is deligthful of how easy it to get something simple running.
[1] https://multicorn.org/
- Creating a Postgres Foreign Data Wrapper
metriql
-
Getting started with a metrics store
Some of the companies that operate in space are Cube Dev; Transform(currently acquired by dbt); metriql. See more companies at https://www.moderndatastack.xyz/companies/metrics-store.
-
Launch HN: Hydra (YC W22) – Query Any Database via Postgres
Presto is pretty successful but its focus is to be distributed query engine, not a proxy layer for the existing query engines. We use Trino ( formerly Presto) as our query layer and do something similar to Hydra at Metriql [1] with a fairly different use-case. Data people provide a semantic layer with the mecrics and expose them to 18+ downstream tools.
[1]: https://metriql.com
-
How do you separate ML from analytics in your data pipeline?
This is why metrics store tooling have started appearing recently (e.g. TransformData, SuperGrain, Metriql, dbt Metrics) - to solve the problem of this table / metric disorganization across an org's data landscape.
-
Open source Business intelligence platform made with Python
We're using Superset to enable our analysts to explore our clients' SEM/SEO/analytics data. It also posts alerts to Slack when, say, the daily session count of a website isn't what was expected given the historical data.
Yeah, it's a little rough to get going, but once it is, we've found it to be a really powerful (and actively developed!) BI tool. It's even better with dbt + MetriQL [0], which can automatically sync Superset's dataset metadata directly with properties you set up in dbt.
Adding custom visualizations is much harder than it should be, but they're very much aware of that, and working to address it. Their Slack community is super-helpful, too.
[0]: https://metriql.com
-
Show HN: Low-Code Metrics Store
As a current Looker power-user, this looks really solid.
One thing I’m not sure about though: can you use the metrics outside of the native tool, and if so how?
That is, I see Looker as a BI tool, not a metrics layer, since you mainly use the metrics you define inside Looker, not in other tools. On the other hand, something like MetriQL[0] is a pure metrics layer that can supposedly be used anywhere.
Is this both? If so, some better documentation around how to use the metrics layer would be helpful (or maybe I just didn’t look in the right place).
[0] https://metriql.com/
-
Notes on the Perfidy of Dashboards
3. Define metrics in one place on top of your data models and expose the metrics to all the data tools. (This layer is new, and we're tapping it at https://metriql.com)
-
Launch HN: Evidence (YC S21) – Web framework for data analysts
We use BSL license and metriql is free with a single database target. If you want to connect multiple dbt projects in a single deployment, you need to go through the sales cycle.
We work with ETL vendors that use metriql to make revenue with our BI tool integrations so we picked BSL license to be able to structure our business model in a way that you should be required to pay only if you're reselling metriql to your customers.
You can find the license here: https://github.com/metriql/metriql
What are some alternatives?
dbeaver - Free universal database tool and SQL client
cube.js - 📊 Cube — The Semantic Layer for Building Data Applications
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
evidence - Business intelligence as code: build fast, interactive data visualizations in pure SQL and markdown
multicorn2
pgx - Build Postgres Extensions with Rust! [Moved to: https://github.com/tcdi/pgrx]
mlcraft - Synmetrix – open source semantic layer / Boost your LLM precision
wundergraph - WunderGraph is a Backend for Frontend Framework to optimize frontend, fullstack and backend developer workflows through API Composition.
examples - Example apps and instrumentation for Honeycomb
gooddata-ui-sdk - GoodData.UI SDK
csv-metabase-driver - A CSV metabase driver