DBMS > Graph Engine vs. Memcached vs. Memgraph vs. SQLite

System Properties Comparison Graph Engine vs. Memcached vs. Memgraph 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

In-memory key-value store, originally intended for caching

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

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Key-value store

Graph DBMS

Relational 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	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	3.19
Rank	#94	Overall
	#8	Graph DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.graphengine.io/docs/manual

github.com/memcached/memcached/wiki

memgraph.com/docs

www.sqlite.org/docs.html

Social network pages

Developer

Microsoft

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Memgraph Ltd

Dwayne Richard Hipp

Initial release

2010

2003

2017

2000

Current release

1.6.27, May 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD license

Open Source

BSL 1.1; commercial license for enterprise edition available

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 and C++

Server operating systems

.NET

FreeBSD
Linux
OS X
Unix
Windows

Linux

server-less

Data scheme

yes

schema-free

schema-free and schema-optional

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

Proprietary protocol

Bolt protocol
Cypher query language

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

dynamic graph partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication using RAFT

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

relationships in graphs

yes

Transaction concepts

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

ACID

with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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 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

yes

using SASL (Simple Authentication and Security Layer) protocol

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.