DBMS > CockroachDB vs. Faircom EDGE vs. SQLite vs. Warp 10

System Properties Comparison CockroachDB vs. Faircom EDGE vs. SQLite vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Widely used embeddable, in-process RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.cockroachlabs.com

www.faircom.com/products/faircom-edge

www.sqlite.org

www.warp10.io

Technical documentation

www.cockroachlabs.com/docs

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Cockroach Labs

FairCom Corporation

Dwayne Richard Hipp

SenX

Initial release

2015

1979

2000

2015

Current release

24.1.0, May 2024

V3, October 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Restricted, free version available

Open Source

Public Domain

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

ANSI C, C++

Java

Server operating systems

Linux
macOS
Windows

Android
Linux

ARM, x86
Raspbian
Windows

server-less

Linux
OS X
Windows

Data scheme

dynamic schema

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes

not rigid because of 'dynamic typing' concept.

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

ANSI SQL queries

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API
Jupyter
WebSocket

Supported programming languages

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

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

.Net, JavaScript, C/C++

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

File partitioning

Customizable business rules for partitioning

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

yes

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.