DBMS > Amazon Redshift vs. Drizzle vs. Google Cloud Bigtable vs. Memgraph

System Properties Comparison Amazon Redshift vs. Drizzle vs. Google Cloud Bigtable vs. Memgraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

Primary database model

Relational DBMS

Key-value store
Wide column store

Graph DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	3.00
Rank	#102	Overall
	#8	Graph DBMS

Website

aws.amazon.com/redshift

cloud.google.com/bigtable

memgraph.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/bigtable/docs

memgraph.com/docs

Social network pages

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Google

Memgraph Ltd

Initial release

2012

2008

2015

2017

Current release

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Free license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

C and C++

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

Linux

Data scheme

yes

schema-free

schema-free and schema-optional

Typing

predefined data types such as float or date

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Bolt protocol
Cypher query language

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

C#
C++
Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

dynamic graph partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationships in graphs

Transaction concepts

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

ACID

Atomic single-row operations

ACID

with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Users, roles and permissions

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.