DBMS > Graphite vs. GridGain vs. Oracle Berkeley DB vs. SAP HANA

System Properties Comparison Graphite vs. GridGain vs. Oracle Berkeley DB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used in-process key-value store

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

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/graphite-project/graphite-web

www.gridgain.com

www.oracle.com/database/technologies/related/berkeleydb.html

www.sap.com/products/hana.html

Technical documentation

graphite.readthedocs.io

www.gridgain.com/docs/index.html

docs.oracle.com/cd/E17076_05/html/index.html

help.sap.com/hana

Developer

Chris Davis

GridGain Systems, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP

Initial release

2006

2007

1994

2010

Current release

GridGain 8.5.1

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

commercial license available

commercial

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

Python

Java, C++, .Net

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux
Unix

Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

yes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HTTP API
Sockets

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

Supported programming languages

JavaScript (Node.js)
Python

C#
C++
Java
PHP
Python
Ruby
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

Triggers

yes (cache interceptors and events)

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

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

Security Hooks for custom implementations

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.