metabase start
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
@@ -0,0 +1,24 @@
|
||||
Title: Metabase and DuckDB
|
||||
Date: 2023-10-18 20:00
|
||||
Modified: 2023-10-18 20:00
|
||||
Category: Business Intelligence
|
||||
Tags: data engineering, Metabase, DuckDB, embedded
|
||||
Slug: metabase-duckdb
|
||||
Authors: Andrew Ridgway
|
||||
Summary: Using Metabase and DuckDB to create an embedded Reporting Container bringing the data as close to the report as possible
|
||||
|
||||
Ahhhh [DuckDB](https://duckdb.org/) if you're even partly floating around in the data space you've probably been hearing ALOT about it and it's _"Datawarehouse on your laptop"_ mantra. However, the OTHER application that sometimes gets missed is _"SQLite for OLAP workloads"_ and it was this concept that once I grasped it gave me a very interesting idea.... What if we could take the very pretty Aggregate Layer of our Data(warehouse/LakeHouse/Lake) and put that data right next to presentation layer of the lake, reducing network latency and... hopefully... have presentation reports running over very large workloads in the blink of an eye. It might even be fast enough that it could be deployed and embedded
|
||||
|
||||
However, for this to work we need some form of conatinerised reporting application.... lucky for us there is [Metabase](https://www.metabase.com/) which is a fantastic little reporting application that has an open core. So this got me thinking... Can I put these two applications together and create a Reporting Layer with report embedding capabilities that is deployable in the cluster and has a admin UI accesible over a web page all whilst keeping the data locked to our network?
|
||||
|
||||
### The Beginnings of an Idea
|
||||
Ok so... Big first question. Can Duckdb and Metabase talk? Well... not quite. But first lets take a quick look at the architecture we'll be employing here
|
||||
|
||||
<img alt="Duckdb Architecture" height="auto" width="100%" src="{attach}/images/metabase_duckdb.png">
|
||||
|
||||
But you'll notice this pretty glossed over line, "Connector", that right there is the clincher. So what is this "Connector"?.
|
||||
|
||||
To Deep dive into this would take a whole blog so to give you something to quickly wrap your head around its the glue that will make metabase be able to query your data source.
|
||||
|
||||
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
Title: Notebook or BI, What is the most appropiate communication medium
|
||||
Date: 2023-07-13 20:00
|
||||
Modified: 2023-07-13 20:00
|
||||
Category: Data Analytics
|
||||
Tags: data engineering, Data Analytics
|
||||
Slug: notebook-or-bi
|
||||
Authors: Andrew Ridgway
|
||||
Summary: When is a notebook enough or when do we need a dashboard
|
||||
|
||||
I want to preface this post by saying I think "Dashboards" or "BI" as terms are wayyyyyyyyyyyyyyyyy over saturated in the market. There seems to be a belief that any question answerable in data deserves the work associated with a dashboard when in fact a simple one off report, or notebook, would be more than enough.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user