DBMS > Axibase vs. CockroachDB vs. GeoSpock vs. SQLite

System Properties Comparison Axibase vs. CockroachDB vs. GeoSpock vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Spatial and temporal data processing engine for extreme data scale

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.cockroachlabs.com

geospock.com

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

www.sqlite.org/docs.html

Developer

Axibase Corporation

Cockroach Labs

GeoSpock

Dwayne Richard Hipp

Initial release

2013

2015

2000

Current release

15585

23.1.1, May 2023

2.0, September 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, Javascript

Server operating systems

Linux

Linux
macOS
Windows

hosted

server-less

Data scheme

yes

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

not rigid because of 'dynamic typing' concept.

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

SQL-like query language

yes, wire compatible with PostgreSQL

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
PHP
Python
R
Ruby

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using RAFT

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Role-based access control

Access rights for users can be defined per table

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.