DBMS > Axibase vs. Elasticsearch vs. FatDB vs. GeoSpock vs. SQLite

System Properties Comparison Axibase vs. Elasticsearch vs. FatDB vs. GeoSpock vs. SQLite

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial and temporal data processing engine for extreme data scale

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Search engine

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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	135.35
Rank	#7	Overall
	#1	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.elastic.co/elasticsearch

geospock.com

www.sqlite.org

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.sqlite.org/docs.html

Developer

Axibase Corporation

Elastic

FatCloud

GeoSpock

Dwayne Richard Hipp

Initial release

2013

2010

2012

2000

Current release

15585

8.6, January 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

Elastic License

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

All OS with a Java VM

Windows

hosted

server-less

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

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

All search fields are automatically indexed

yes

temporal, categorical

yes

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

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

Java API
RESTful HTTP/JSON API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

via applications

Triggers

yes

by using the 'percolation' feature

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
Immediate Consistency

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.

Memcached and Redis integration

yes

User concepts

Access control

Can implement custom security layer via applications

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.