ActorDB vs CockroachDB Cloud

ActorDB is an open-source distributed relational SQL database from Biokoda that organizes data into independent actors. SQLite handles SQL queries and LMDB provides storage. Applications connect through the MySQL protocol or Thrift, and the FAQ recommends Thrift; default MySQL drivers also work. ActorDB uses Raft for distributed consensus and write replication, and describes itself as strongly consistent. Transactions can span multiple actors and are described as ACID compliant. It can also provide a sharded key-value store with structured values, multiple columns, and foreign tables. The maker says horizontal scaling can reach hundreds of nodes and petabytes when data is spread across actors. If a server fails, a follower can lead an actor while a cluster majority remains online. Recommended cluster sizes are 1, 3, or 5 nodes. Supported downloads include Windows, Mac OS X, CentOS, and Ubuntu, with version 0.10.29 dated 1 October 2019 shown as the latest stable release.

CockroachDB Cloud is a managed distributed SQL platform for development, testing, and production workloads. It provisions clusters, scales compute and storage, performs rolling upgrades, and manages backups. The database supports ACID transactions and can scale reads and writes horizontally without manual sharding. Deployments can span AWS, Azure, and GCP, including multiple providers and regions. Cockroach Labs' Terraform provider and Cloud APIs support operation automation. Security features include TLS for traffic between clients and servers and between nodes, cloud-provider disk encryption at rest, and column-level encryption. The listed plans include Basic at free and Standard at $0.06 a month; usage is metered by the minute, billed monthly, and rates vary by region. New Cloud organizations receive a 30-day trial with $400 in credits. The trial ends after 30 days or when the credits run out, and clusters are then paused. Pricing terms also distinguish deployments created before and from September 15, 2026, so the applicable plan depends on deployment timing.