|
5 | 5 | </picture> |
6 | 6 | </div> |
7 | 7 |
|
8 | | -> _Query everything — **instantly**._ |
9 | 8 |
|
10 | 9 | # RivetDB |
11 | 10 |
|
12 | | -Query everything — instantly. |
| 11 | +> _Query everything — **instantly**._ |
13 | 12 |
|
14 | 13 | RivetDB is a high-performance, federated query engine built on a smart, just-in-time cache. |
15 | | -It provides a Trino-style SQL interface for querying remote data sources without needing heavy infrastructure. |
16 | | -The goal is to unify data access across systems while still getting fast, reliable performance on a single node. |
17 | 14 |
|
18 | | -RivetDB takes insperation from the [DuckDB](https://duckdb.org/) and SmallData community, which has shown how much you can get out of a single machine when you pair simplicity, vectorized execution, and efficient columnar formats. RivetDB applies that same thinking to federated data, using Arrow-native execution to make remote sources feel local. We think this is going to be especially important as agents query disparate systems and want to avoid scattering data fetching logic. |
| 15 | +It provides a Trino-style SQL interface for querying remote data sources without needing heavy infrastructure. The goal is to unify data access across systems while still getting fast, reliable performance on a single node. |
| 16 | + |
| 17 | +RivetDB takes inspiration from [DuckDB](https://duckdb.org/) and the Small Data community, which has shown how much you can get out of a single machine when you pair simplicity, vectorized execution, and efficient columnar formats. RivetDB applies that same thinking to federated data, using Arrow-native execution to make remote sources feel local. We think this is going to be especially important as agents query disparate systems and want to avoid scattering data fetching logic. |
19 | 18 |
|
20 | 19 | Under the hood, RivetDB is built in Rust and powered by [Apache DataFusion](https://datafusion.apache.org/). The combination gives us strong safety guarantees, solid performance, and a proven execution engine that plays well with Arrow. |
21 | 20 |
|
22 | 21 | RivetDB is under active development, and the APIs will continue to shift as we move toward a stable 1.0 release. |
23 | | -ment, and the APIs will continue to shift as we move toward a stable 1.0 release. |
24 | | - |
25 | 22 |
|
26 | 23 | > **🚧 Early Development:** We are targeting a public preview with caching, lookup APIs, and a CLI in **Q1 2026**. |
27 | 24 | > Expect breaking changes until the API surface stabilizes. |
@@ -68,11 +65,11 @@ RivetDB aims to become a unified query engine that eliminates challenges working |
68 | 65 |
|
69 | 66 | - A consistent SQL interface for structured, semi-structured, and remote data sources |
70 | 67 | - Intelligent caching that adapts to query patterns and reduces data movement |
71 | | -- Tight integration with modern data platforms |
72 | | -- Tooling that gives developers fast introspection into data, metadata, and performance |
73 | | -- Clear APIs and predictable behavior |
| 68 | +- Tooling that gives developers introspection into data, metadata, and performance |
| 69 | +- Millisecond startup times for on-demand ephemeral compute |
| 70 | +- Developer-friendly documentation and APIs |
74 | 71 |
|
75 | | -The long-term trajectory includes distributed caching, richer connectors, real-time introspection, and seamless orchestration integration. |
| 72 | +The long-term goal includes distributed caching, additional connectors, real-time introspection, and seamless orchestration integration. |
76 | 73 |
|
77 | 74 | --- |
78 | 75 |
|
|
0 commit comments