DBMS > CouchDB vs. SAP Advantage Database Server vs. SQLite vs. TigerGraph

System Properties Comparison CouchDB vs. SAP Advantage Database Server vs. SQLite vs. TigerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Low-cost RDBMS with access to ISAM and FoxPro data structures

Widely used embeddable, in-process RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

couchdb.apache.org

www.sap.com/products/advantage-database-server.html

www.sqlite.org

www.tigergraph.com

Technical documentation

docs.couchdb.org/en/stable

www.sqlite.org/docs.html

docs.tigergraph.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Sybase, SAP

Dwayne Richard Hipp

Initial release

2005

1993

2000

2017

Current release

3.3.3, December 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Public Domain

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

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Delphi
Perl
PHP

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

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

caching of (temporary) tables can be configured

yes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Role-based access control

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.