DBMS > Graph Engine vs. LevelDB vs. Postgres-XL vs. SQLite

System Properties Comparison Graph Engine vs. LevelDB vs. Postgres-XL vs. SQLite

Please select another system to include it in the comparison.

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

github.com/google/leveldb

www.postgres-xl.org

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

github.com/google/leveldb/blob/main/doc/index.md

www.postgres-xl.org/documentation

www.sqlite.org/docs.html

Developer

Microsoft

Google

Dwayne Richard Hipp

Initial release

2010

2011

2014

since 2012, originally named StormDB

2000

Current release

1.23, February 2021

10 R1, October 2018

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD

Open Source

Mozilla public license

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

Illumos
Linux
OS X
Windows

Linux
macOS

server-less

Data scheme

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

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

with automatic compression on writes

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

fine grained access rights according to SQL-standard

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.