Trino
cube.js
Our great sponsors
Trino | cube.js | |
---|---|---|
44 | 86 | |
9,519 | 17,120 | |
2.8% | 1.1% | |
10.0 | 9.9 | |
3 days ago | about 4 hours ago | |
Java | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
Trino
- Trino: Fast distributed SQL query engine for big data analytics
-
Game analytic power: how we process more than 1 billion events per day
We decided not to waste time reinventing the wheel and simply installed Trino on our servers. It’s a full featured SQL query engine that works on your data. Now our analysts can use it to work with data from AppMetr and execute queries at different levels of complexity.
-
Your Thoughts on OLAPs Clickhouse vs Apache Druid vs Starrocks in 2023/2024
DevRel for StarRocks. Trino doesn't have a great caching layer (https://github.com/trinodb/trino/pull/16375) and performance (https://github.com/trinodb/trino/issues/14237) and https://github.com/oap-project/Gluten-Trino. In benchmarks and community user testing, StarRocks has outperformed.
-
Making Hard Things Easy
What if my SQL engine is Presto, Trino [1], or a similar query engine? If it's federating multiple source databases we peel the SQL back and get... SQL? Or you peel the SQL back and get... S3 + Mongo + Hadoop? Junior analysts would work at 1/10th the speed if they had to use those raw.
- Trino, a open query engine that runs at ludicrous speed
-
Questions about Athena, Trino and Iceberg
The good thing is that the concepts in terms to the SQL supported by Trino transfers between them all. So its completely reasonable to start with one and move to another. In fact that is something that happens regularly. I invite to you check out the talks from the Trino Fest event that is just wrapping up today. There are presentations about all these aspects and different scenarios users encounter. All videos and slides will go live on the Trino website soon. Also feel free to join the Trino slack to chat about about all this with other users.
-
Multi-Databases across Multiple Servers - MySQL
There are distributed query engines like Trino that help with this sort of problem https://trino.io/
-
Iceberg on Cloudtrail Logs with Athena
This issue in particular is a killer for me: https://github.com/trinodb/trino/issues/10974
-
Data Lake, Real-time Analytics, or Both? Exploring Presto and ClickHouse
AFAIK Presto was forked and Trino https://trino.io/ is now the leading SQL Query engine .
-
Apache Iceberg as storage for on-premise data store (cluster)
Trino or Hive for SQL querying. Get Trino/Hive to talk to Nessie.
cube.js
-
MQL – Client and Server to query your DB in natural language
I should have clarified. There's a large number of apps that are:
1. taking info strictly from SQL (e.g. information_schema, query history)
2. taking a user input / question
3. writing SQL to answer that question
An app like this is what I call "text-to-sql". Totally agree a better system would pull in additional documentation (which is what we're doing), but I'd no longer consider it "text-to-sql". In our case, we're not even directly writing SQL, but rather generating semantic layer queries (i.e. https://cube.dev/).
-
Show HN: Spice.ai – materialize, accelerate, and query SQL data from any source
I'm not too familiar with https://cube.dev/ - but my initial impression is they are focused more on providing APIs backed by SQL. They have a SQL API that emulates the PostgreSQL wire protocol, whereas Spice implements Arrow and Flight SQL natively. Their pre-aggregations are a similar concept to Spice's data accelerators. It also looks like they have their own query language, whereas Spice is native SQL as well.
-
Show HN: Delphi – Build customer-facing AI data apps (that work)
Hey HN!
Over the past year, my co-founder David and I have been building Delphi to let developers create amazing customer-facing AI experiences on top of their data. We're excited to share it with you.
David and I have spent our careers leading data and engineering teams. After ChatGPT got popular, we saw a rush of "chat with your data" startups launch. Most of these are "text-to-SQL" and use an LLM like GPT-4 to generate SQL queries that run directly against a data warehouse or database.
However, the general perception now is most of them make for nice demos but are hard to make work in the real world. The reason is data complexity. Even smart LLMs find it difficult to reason about messy databases with hundreds of tables, thousands of columns, and complex schemas that have been built up piece-meal for years. Text-to-SQL can be a fine dev tool for data scientists and analysts, but we've seen many organizations hesitate to deploy it to end users, who never know if the answer they get one day will be the same the next.
David and I found a better way. From our time in the data engineering world, we were familiar with a type of tool called "semantic layers." Think of them like an ORM for analytics. Basically, they sit between databases (or data warehouses) and data consumers (data viz tools like Tableau or APIs) and map real-world concepts (entities like "customers" and metrics like "sales") to database tables and calculations.
Semantic layers are often used for "embedded analytics" (e.g. when you're building customer-facing dashboards into your application) but are increasingly also used for traditional business intelligence. Cube (https://cube.dev) is a prominent example, and dbt has also recently released one. They're useful because with a semantic layer, the consumer doesn't have to think about questions like "how do we define revenue?" when running a query. They just get consistent, governed data definitions across their business.
We realized that semantic layers could be just as useful for LLMs as for humans. After all, LLMs are built on natural language, so a system that deterministically translates natural language concepts into code has obvious power when you're working with LLMs. With a semantic layer, we've found that companies can get AI to answer much more complex questions than without it.
For a year now, we've been building Delphi to do just that. We've gone through a few iterations/pivots (initially we were focused on building a Slack bot for internal analytics) and are now seeing our developer-first approach resonate. We're being used to power customer-facing fintech applications, recruiting software, and more.
How do you use Delphi? The first step is connecting your database; then, we build your semantic layer on top of it. Right now we do this manually, but we're moving more and more of it over to AI. Once that's done, we have 3 main ways of using Delphi: 1) white-labeling our AI analytics platform and providing it to your customers; 2) a streaming REST API and SDKs; and 3) React components to easily drop a "chat with your data" experience into your app.
If this is interesting to you, drop us a line at [email protected] or sign up at our website (https://delphihq.com) to get in touch. Thanks for reading! Would love to hear any thoughts and feedback.
-
Apache Superset
We use https://cube.dev/ as intermediate layer between data warehouse database and Superset (and other "terminal" apps for BI like report generators). You define your schema (metrics, dimensions, joins, calculated metrics etc) in cube and then access them by any tool that can connect to SQL db
-
Need to reduce costs - which service to use?
also check out cube.dev. they can do the semantic layer and cache it so you are not hitting Snowflake all the time.
-
Anyone with experience moving to Cube.dev + Metabase/Superset from Looker ?
We need metrics to live in source control with reviews. Metabase doesn't have a git integration for metrics, which is why we are convinced to use cube.dev as a semantic layer.
-
GigaOm Sonar Report Reviews Semantic Layer and Metric Store Vendors
https://github.com/cube-js/cube comes out very well at the end as a promising open source system, getting rather close to the bullseye. Would love to know more & hear people's experience with it.
-
Show HN: VulcanSQL – Serve high-concurrency, low-latency API from OLAP
How is this different from something like https://cube.dev/
-
Best Headless Chart Library?
Have a look to cube.js
-
Advice / Questions on Modern Data Stack
For now, I've been thinking on using self-hosted Rudderstack both for ingestion and reverse ETL, cube.dev as the abstraction later for building webapps and providing catching for the BI layer, and dbt for transformations. But I have doubts with the following elements:
What are some alternatives?
Apache Spark - Apache Spark - A unified analytics engine for large-scale data processing
Apache Superset - Apache Superset is a Data Visualization and Data Exploration Platform [Moved to: https://github.com/apache/superset]
dremio-oss - Dremio - the missing link in modern data
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
Presto - The official home of the Presto distributed SQL query engine for big data
Redash - Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
Apache Drill - Apache Drill is a distributed MPP query layer for self describing data
Druid - Apache Druid: a high performance real-time analytics database.
Apache Calcite - Apache Calcite
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
ClickHouse - ClickHouse® is a free analytics DBMS for big data
metriql - The metrics layer for your data. Join us at https://metriql.com/slack