Skip to content

Commit ff767d2

Browse files
authored
Remove duplicate text (#31)
* Remove duplicate text * Clean up language and clarify vision --------- Co-authored-by: Eddie Tejeda <[email protected]>
1 parent 8a626a5 commit ff767d2

File tree

1 file changed

+8
-11
lines changed

1 file changed

+8
-11
lines changed

README.md

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,20 @@
55
</picture>
66
</div>
77

8-
> _Query everything — **instantly**._
98

109
# RivetDB
1110

12-
Query everything — instantly.
11+
> _Query everything — **instantly**._
1312
1413
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.
1714

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.
1918

2019
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.
2120

2221
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-
2522

2623
> **🚧 Early Development:** We are targeting a public preview with caching, lookup APIs, and a CLI in **Q1 2026**.
2724
> Expect breaking changes until the API surface stabilizes.
@@ -68,11 +65,11 @@ RivetDB aims to become a unified query engine that eliminates challenges working
6865

6966
- A consistent SQL interface for structured, semi-structured, and remote data sources
7067
- 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
7471

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.
7673

7774
---
7875

0 commit comments

Comments
 (0)