nodejs-bigquery
cube.js
Our great sponsors
nodejs-bigquery | cube.js | |
---|---|---|
43 | 86 | |
457 | 17,135 | |
1.8% | 1.2% | |
8.0 | 9.9 | |
3 days ago | 4 days ago | |
TypeScript | 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.
nodejs-bigquery
-
Wrangling BigQuery at Reddit
If you've ever wondered what it's like to manage a BigQuery instance at Reddit scale, know that it's exactly like smaller systems just with much, much bigger numbers in the logs. Database management fundamentals are eerily similar regardless of scale or platform; BigQuery handles just about anything we throw at it, and we do indeed throw it the whole book. Our BigQuery platform is more than 100 petabytes of data that supports data science, machine learning, and analytics workloads that drive experiments, analytics, advertising, revenue, safety, and more. As Reddit grew, so did the workload velocity and complexity within BigQuery and thus the need for more elegant and fine-tuned workload management.
-
Building a dev.to analytics dashboard using OpenSearch
Now I know I've got some data I could use, I now need to find a platform that I can use to analyse the data coming from the Forem API. I did consider some other pieces of software, such as Google BigQuery (with looker studio) and ElasticSearch (with Kibana), I ultimately went with OpenSearch which is essentially a forked version of ElasticSearch maintained by AWS. The main reasons are that I could host it locally for free (unlike BigQuery). I do have some prior experience with both elastic (back when it was called ELK) and OpenSearch, but my work with OpenSearch was far more recent, so I decided to go with that.
- Como evitar SQL Injection utilizando client do BigQuery
- Learning Excel. Is there a resource for fake data sets like retail and wholesale inventories and sales histories etc for testing and practice?
-
How to Totally Fubar Your Cloud Infrastructure Costs
First, in one of our recent projects, we helped our client to run the cloud-based infrastructure of their entirely automated, real-time SEO platform. The solution rested in the safe familiarity of Googleβs popular cloud-based data centres (i.e. Google Cloud Platform), whilst also making use of BigQuery β a serverless, multi-cloud data warehouse.
-
Data Analytics at Potloc I: Making data integrity your priority with Elementary & Meltano
Bigquery as our data warehouse
-
I've tried really hard but need some help please. Bigquery not returning data after 2019.
This post in github thinks it may be an error in bigquery's backend.
-
Deploying a Data Warehouse with Pulumi and Amazon Redshift
A data warehouse is a specialized database that's purpose built for gathering and analyzing data. Unlike general-purpose databases like MySQL or PostgreSQL, which are designed to meet the real-time performance and transactional needs of applications, a data warehouse is designed to collect and process the data produced by those applications, collectively and over time, to help you gain insight from it. Examples of data-warehouse products include Snowflake, Google BigQuery, Azure Synapse Analytics, and Amazon Redshift β all of which, incidentally, are easily managed with Pulumi.
- [Question] Which GCP tool should I use to build a Business decisional dashboard?
-
Designing a Video Streaming Platform πΉ
Google BigQuery
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?
airbyte - The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
Apache Superset - Apache Superset is a Data Visualization and Data Exploration Platform [Moved to: https://github.com/apache/superset]
dbt-core - dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
dagster - An orchestration platform for the development, production, and observation of data assets.
Druid - Apache Druid: a high performance real-time analytics database.
rudderstack-docs - Documentation repository for RudderStack - the Customer Data Platform for Developers.
Redash - Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
dbt - dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. [Moved to: https://github.com/dbt-labs/dbt-core]
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
streamlit - Streamlit β A faster way to build and share data apps.
metriql - The metrics layer for your data. Join us at https://metriql.com/slack