DBMS > Graph Engine vs. jBASE vs. MarkLogic vs. Prometheus vs. SQLite

System Properties Comparison Graph Engine vs. jBASE vs. MarkLogic vs. Prometheus vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A robust multi-value DBMS comprising development tools and middleware

Operational and transactional Enterprise NoSQL database

Open-source Time Series DBMS and monitoring system

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Multivalue DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Time Series DBMS

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.marklogic.com

prometheus.io

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.marklogic.com

prometheus.io/docs

www.sqlite.org/docs.html

Developer

Microsoft

Rocket Software (formerly Zumasys)

MarkLogic Corp.

Dwayne Richard Hipp

Initial release

2010

1991

2001

2015

2000

Current release

5.7

11.0, December 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

Apache 2.0

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

.NET and C

C++

Server operating systems

.NET

AIX
Linux
Windows

Linux
OS X
Windows

Linux
Windows

server-less

Data scheme

yes

schema-free

Schema can be enforced

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

.Net
Basic
Jabbascript
Java

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
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 XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by Federation

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

yes, with Range Indexes

yes

User concepts

Access control

Access rights can be defined down to the item level

Role-based access control at the document and subdocument levels

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.