Mosaic is an extensible architecture for linking data visualizations, tables, input widgets, and other data-driven components, leveraging a backing database for scalable processing of both static and interactive views. With Mosaic, you can visualize and explore millions and even billions of data points at interactive rates.
The key idea is to have interface components "publish" their data needs as declarative queries that can be managed, optimized, and cross-filtered by a coordinator that proxies access to DuckDB.
Learn more about Mosaic at the documentation site, or read the Mosaic research paper.
If referencing Mosaic, please use the following citation:
@article{heer2024mosaic,
title={Mosaic: An Architecture for Scalable \& Interoperable Data Views},
author={Heer, Jeffrey and Moritz, Dominik},
journal={IEEE Transactions on Visualization and Computer Graphics},
year={2024},
volume={30},
number={1},
pages={436-446},
doi={10.1109/TVCG.2023.3327189}
}
This repository contains a set of related packages, spanning the core Mosaic architecture, DuckDB servers, the vgplot visualization library, and example projects.
Mosaic Architecture (packages/mosaic)
mosaic-core: The core Mosaic components. A central coordinator, parameters and selections for linking scalar values or query predicates (respectively) across Mosaic clients, and filter groups with materialized views of pre-aggregated data. The Mosaic coordinator can send queries either over the network to a backing server (socket and rest clients) or to a client-side DuckDB-WASM instance (wasm client).mosaic-sql: An API for convenient construction and analysis of SQL queries. Query objects then coerce to SQL query strings.packages/vgplot)
vgplot is a visualization grammaer API that demonstrates the features and performance of the Mosaic architecture. It includes a layered grammar of interactive graphics alongside table and input widget components. For convenience, the vgplot package re-exports much of the mosaic-core, mosaic-sql, mosaic-plot, and mosaic-inputs packages. For most vgplot applications, it is sufficient to either import @uwdata/vgplot alone or in conjunction with @uwdata/mosaic-spec.
vgplot: A visualization grammar API for building interactive Mosaic-powered visualizations and dashboards. This package provides convenient, composable methods that combine multiple Mosaic packages (core, inputs, plot, etc.) in an integrated API. This API re-exports much of the mosaic-core, mosaic-sql, mosaic-plot, and mosaic-inputs packages, enabling use in a stand-alone fashion.mosaic-inputs: Standalone data-driven components such as input menus, text search boxes, and sortable, load-on-scroll data tables.mosaic-plot: An interactive grammar of graphics implemented on top of Observable Plot. Marks (plot layers) serve as individual Mosaic clients. These marks can push data processing (binning, hex binning, regression) and optimizations (such as M4 for line/area charts) down to the database. This package also provides interactors for linked selection, filtering, and highlighting using Mosaic Params and Selections.mosaic-spec: Declarative specification of Mosaic-powered applications as JSON or YAML files. This package provides a parser and code generation framework for reading specifications in a JSON format and generating live Mosaic visualizations and dashboards using the vgplot API.widget: A Jupyter widget for Mosaic. Given a declarative specification, will generate web-based visualizations while leveraging DuckDB in the Jupyter kernel. Create interactive Mosaic plots over Pandas and Polars data frames or DuckDB connections.packages/server)
duckdb-server: A Python-based server that runs a local DuckDB instance and support queries over Web Sockets or HTTP, returning data in either Apache Arrow or JSON format.duckdb-server-rust: A Rust-based server similar to duckdb-server (Python) and mosaic-duckdb (Node.js) with additional support for HTTP/2. We are still evaluating what server component works best. DuckDB support for Rust is often delayed compared to Python.mosaic-duckdb: A Promise-based Node.js API to DuckDB, along with a data server that supports transfer of Apache Arrow and JSON data over either Web Sockets or HTTP. Due to quality and maintenance issues involving the Node.js DuckDB client and Arrow extension, we recommend using the Python-based duckdb-server package instead. However, we retain this package for both backwards compatibility and internal testing use.packages/examples)
vanilla-example: A basic example demonstrating how to deploy Mosaic in a website.svelte-example: An example application that demonstrates howto create Mosaic components within web frameworks such as Svelte and React.vega-example: A proof-of-concept example integrating Vega-Lite with Mosaic for data management and cross-view linking.To build and develop Mosaic locally:
npm i to install dependencies.npm test to run the test suite.npm run build to build client-side bundles.uv build --all-packages to build the Python packages.To run local interactive examples:
npm run dev to launch a local web server and view examples. By default, the examples use DuckDB-WASM in the browser. For greater performance, launch and connect to a local DuckDB server as described below.To launch a local DuckDB server:
npm run server to launch the duckdb-server. This runs the server in development mode, so the server will restart if you change its code.To use Mosaic with DuckDB Python in Jupyter Notebooks:
widget documentation.To use Mosaic with DuckDB-WASM in Observable Notebooks:
To use Mosaic and DuckDB in Observable Framework:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4