DBMS > CouchDB vs. Google Cloud Datastore vs. Memgraph vs. SAP HANA

System Properties Comparison CouchDB vs. Google Cloud Datastore vs. Memgraph vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

An open source graph database built for real-time streaming and compatible with Neo4j

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

Primary database model

Document store

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.02
Rank	#98	Overall
	#8	Graph DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

cloud.google.com/datastore

memgraph.com

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

memgraph.com/docs

help.sap.com/hana

Social network pages

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

Memgraph Ltd

SAP

Initial release

2005

2008

2017

2010

Current release

3.3.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

BSL 1.1; commercial license for enterprise edition available

commercial

Cloud-based only

Only available as a cloud service

yes

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

Erlang

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Appliance or cloud-service

Data scheme

schema-free

schema-free and schema-optional

yes

Typing

predefined data types such as float or date

yes, details here

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Bolt protocol
Cypher query language

JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

View functions in JavaScript

using Google App Engine

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

dynamic graph partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

Multi-source replication using RAFT

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

relationships in graphs

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

with periodic snapshot and write-ahead logging (WAL) of changes

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

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users, roles and permissions

yes

More information provided by the system vendor

Specific characteristics

Memgraph directly connects to your streaming infrastructure so you and your team...
» more

Competitive advantages

Business Source License ensures a future for the Memgraph community MAGE algorithm...
» more

Typical application scenarios

Graph algorithms in bioinformatics Social network analysis Cryptocurrency network...
» more

Licensing and pricing models

You can check out our pricing model and licenses on the company website .
» more

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.