Ross ROSS = Recommend OSS · open-source software intelligence for agents

slatedb/slatedb

A cloud native embedded storage engine built on object storage. observed · 2026-08-28

github.com/slatedb/slatedb · homepage · Rust · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

90/100

  • Activity 99
  • Release rhythm 95
  • Longevity 63
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 18.5
  • age_days: 890
  • days_rel: 35
  • days_push: 7
  • n_releases_24m: 27

Full methodology

Adoption not part of the score

3356 stars · 289 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

SlateDB is an embedded key-value storage engine implemented in Rust as a log-structured merge-tree (LSM) that persists all data to object storage like S3, GCS, and Azure Blob instead of local disks. It offers single-writer/multiple-reader semantics, snapshot isolation, transactions, read caching, and zero-copy clones, with official bindings for Go, Java, Node.js, and Python.

Use cases

  • build a key-value database with bottomless storage on S3
  • replace RocksDB where local disks are undesirable
  • store application state durably in object storage without running a database server
  • scale read traffic with multiple readers against one shared dataset
  • create zero-copy database clones or forks from checkpoints
  • tune write durability versus API cost for cloud-native workloads

When to choose

  • you want an embedded LSM engine with no local disk or replication protocol
  • you need the durability and economics of S3-class object storage
  • you want single-writer with multiple read replicas backed by a shared object store
  • you need snapshot isolation, transactions, or cheap zero-copy clones

When to avoid

  • you need low-latency writes; object store PUT latency (50-100ms on standard tiers) dominates
  • your workload is write-heavy and object store API costs or rate limits would be prohibitive
  • you need multi-writer concurrency or a full SQL database
  • you need a mature battle-tested engine like RocksDB for latency-critical local storage

Facets

library · maturity active

database caching serialization databases cloud-computing developer-tools microservices rust go python jvm cross-platform cloud lsm-tree object-storage embedded-database key-value-store storage-engine s3 rocksdb-alternative zero-disk snapshot-isolation nodejs

10 sources

Member repositories

RepositoryRoleHealth v2
slatedb/slatedbmain90

For agents

markdown · JSON · MCP: product_card(name="slatedb/slatedb")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem