DBMS > AlaSQL vs. Couchbase vs. Datomic vs. GridGain

System Properties Comparison AlaSQL vs. Couchbase vs. Datomic vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Key-value store
Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

docs.couchbase.com

docs.datomic.com

www.gridgain.com/docs/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Couchbase, Inc.

Cognitect

GridGain Systems, Inc.

Initial release

2014

2011

2012

2007

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

1.0.6735, June 2023

GridGain 8.5.1

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

limited edition free

commercial

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

JavaScript

C, C++, Go and Erlang

Java, Clojure

Java, C++, .Net

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JavaScript API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

JavaScript

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

Transaction Functions

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

via the TAP protocol

By using transaction functions

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

none

But extensive use of caching in the application peers

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

none

But extensive use of caching in the application peers

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

recommended only for testing and development

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Security Hooks for custom implementations

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.