DBMS > AllegroGraph vs. CouchDB vs. EJDB vs. SQLite

System Properties Comparison AllegroGraph vs. CouchDB vs. EJDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used embeddable, in-process RDBMS

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

allegrograph.com

couchdb.apache.org

github.com/Softmotions/ejdb

www.sqlite.org

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

docs.couchdb.org/en/stable

github.com/Softmotions/ejdb/blob/master/README.md

www.sqlite.org/docs.html

Developer

Franz Inc.

Apache Software Foundation

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

Softmotions

Dwayne Richard Hipp

Initial release

2004

2005

2012

2000

Current release

8.0, December 2023

3.3.3, December 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Apache version 2

Open Source

GPLv2

Open Source

Public Domain

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

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

RDF schemas

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

bulk load of XML files possible

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API
SPARQL

RESTful HTTP/JSON API

in-process shared library

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
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

JavaScript or Common Lisp

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

improved architecture with release 2.0

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Read/Write Locking

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

News

How a Neuro-Symbolic AI Approach Can Improve Trust in AI Apps
23 May 2024

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

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.