DBMS > Graph Engine vs. Postgres-XL vs. SAP HANA vs. Solr

System Properties Comparison Graph Engine vs. Postgres-XL vs. SAP HANA vs. Solr

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

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

In-memory, column based data store. Available as appliance or cloud service

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

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

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

www.graphengine.io

www.postgres-xl.org

www.sap.com/products/hana.html

solr.apache.org

Technical documentation

www.graphengine.io/docs/manual

www.postgres-xl.org/documentation

help.sap.com/hana

solr.apache.org/resources.html

Developer

Microsoft

SAP

Apache Software Foundation

Initial release

2010

2014

since 2012, originally named StormDB

2010

2006

Current release

10 R1, October 2018

2.0 SPS07 (April 4, 2023), April 2023

9.5.0, February 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Mozilla public license

commercial

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

Java

Server operating systems

.NET

Linux
macOS

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

distributed, parallel query execution

yes

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

user defined functions

SQLScript, R

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.