TreodeDB
discontinuedby Treode, Inc. · since 2014 · also known as Treode, Treode Store
Replicated, sharded key-value store with multi-row atomic writes for REST services; abandoned in 2015.
discontinued. Last release 0.2.0 (Dec 2014) and last commit Oct 2015; Treode's domain has lapsed. Consider FoundationDB or TiKV.
Overview
TreodeDB was a distributed key-value store written in Scala by Treode, Inc. It replicated and sharded data across a cluster and offered conditional batch writes, multi-row atomic updates guarded by read timestamps, which let REST services extend optimistic concurrency through caches and CDNs using ETag-style versions. It kept versioned data and could feed Spark RDDs, DStreams and Hadoop InputFormats for analytics. Only 0.1 and 0.2 releases shipped (2014); commits ended in late 2015 and the company domain has lapsed. It remains a readable example of a transactional, versioned KV design.
Strengths & trade-offs
Strengths
- +Multi-row atomic writes with optimistic concurrency, unusual for a KV store of its time
- +Versioned data designed to work with HTTP caches and CDNs
- +Connectors for Spark and Hadoop analytics
Trade-offs
- −Pre-1.0 and abandoned since 2015
- −No community, packages or documentation site still online
Great for
- +Studying conditional batch writes and versioned KV design
- +Reference Scala code for a replicated, sharded store
Think twice for
- −Production use
Capabilities
Native or official first-party support · 2 of 25 tracked
Scale & consistency
- Comfortable data size
- Small · ≤ 100 GB
- Horizontal scaling
- Native
- Multi-region
- No
- Transactions
- Full ACID
- Consistency
- Strong
- Schema
- Schemaless
- Architecture
- Distributed
- Query languages
- Scala/Java API, REST
Designed for sharding and replication but never proven at scale before development stopped.
Deployment
Ecosystem
Alternatives to TreodeDB
Apple's ordered, strictly serializable distributed key-value store, built to have layers on top.
treodedb vs foundationdb →CNCF-graduated, Raft-replicated transactional key-value store in Rust; the storage layer of TiDB.
treodedb vs tikv →Postgres-wire distributed SQL built to survive node, zone and region failures with serializable transactions.
treodedb vs cockroachdb →Masterless wide-column database built for always-on writes across data centers.
treodedb vs apache-cassandra →FIS's high-throughput M (MUMPS) database and compiler, behind major core-banking systems.
treodedb vs gt-m →Open-source MUMPS/M hierarchical key-value database forked from GT.M, with SQL via Octo.
treodedb vs yottadb →TreodeDB FAQ
What is TreodeDB?
TreodeDB is a key-value database by Treode, Inc., first released in 2014. TreodeDB was a distributed key-value store written in Scala by Treode, Inc. It replicated and sharded data across a cluster and offered conditional batch writes, multi-row atomic updates guarded by read timestamps, which let REST services extend optimistic concurrency through caches and CDNs using ETag-style versions. It kept versioned data and could feed Spark RDDs, DStreams and Hadoop InputFormats for analytics. Only 0.1 and 0.2 releases shipped (2014); commits ended in late 2015 and the company domain has lapsed. It remains a readable example of a transactional, versioned KV design.
Is TreodeDB open source?
Yes. TreodeDB is open source. License: Apache License 2.0.
Does TreodeDB support ACID transactions?
Yes. TreodeDB supports full ACID transactions, with strong consistency.
Does TreodeDB scale horizontally?
TreodeDB scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at small scale (≤ 100 GB).
How can I run TreodeDB?
You can self-host it.
What is TreodeDB best for?
TreodeDB is a strong fit for studying conditional batch writes and versioned KV design; and reference Scala code for a replicated, sharded store. Think twice for production use.
What are the best alternatives to TreodeDB?
Common alternatives to TreodeDB include FoundationDB, TiKV, CockroachDB, Apache Cassandra and GT.M. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
Is TreodeDB still maintained?
TreodeDB is discontinued. Last release 0.2.0 (Dec 2014) and last commit Oct 2015; Treode's domain has lapsed. Consider FoundationDB or TiKV.
How popular is TreodeDB?
TreodeDB ranks #627 of 844 databases on the WhichDB Score (0.6/100), and #114 among key-value databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.