DBMS > Drizzle vs. JanusGraph vs. OpenEdge vs. SQLite

System Properties Comparison Drizzle vs. JanusGraph vs. OpenEdge vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Application development environment with integrated database management system

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

janusgraph.org

www.progress.com/openedge

www.sqlite.org

Technical documentation

docs.janusgraph.org

documentation.progress.com/output/ua/OpenEdge_latest

www.sqlite.org/docs.html

Developer

Drizzle project, originally started by Brian Aker

Linux Foundation; originally developed as Titan by Aurelius

Progress Software Corporation

Dwayne Richard Hipp

Initial release

2008

2017

1984

2000

Current release

7.2.4, September 2012

1.0.0, October 2023

OpenEdge 12.2, March 2020

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

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

C++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

AIX
HP-UX
Linux
Solaris
Windows

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Java
PHP

Clojure
Java
Python

Progress proprietary ABL (Advanced Business Language)

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

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

User authentification and security via Rexster Graph Server

Users and groups

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.