DBMS > Apache Druid vs. IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Neo4j

System Properties Comparison Apache Druid vs. IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Neo4j

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Database as a Service offering based on Apache CouchDB

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Globally distributed, horizontally scalable, multi-model database service

Scalable, ACID-compliant graph database designed with a high-performance distributed cluster architecture, available in self-hosted and cloud offerings

Primary database model

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	44.47
Rank	#23	Overall
	#1	Graph DBMS

Website

druid.apache.org

www.ibm.com/products/cloudant

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/cosmos-db

neo4j.com

Technical documentation

druid.apache.org/docs/latest/design

cloud.ibm.com/docs/Cloudant

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

neo4j.com/docs

Developer

Apache Software Foundation and contributors

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Neo4j, Inc.

Initial release

2012

2010

1992

2014

2007

Current release

29.0.1, April 2024

1902 (16.0.11328.20222), March 2019

5.18.1, March 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Bundled with Microsoft Office

commercial

Open Source

GPL version3, commercial licenses 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.

Neo4j Aura: Neo4j’s fully managed cloud service: The zero-admin, always-on graph database for cloud developers.

Implementation language

Java

Erlang

C++

Java, Scala

Server operating systems

Linux
OS X
Unix

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Can also be used server-less as embedded Java database.
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

schema-free and schema-optional

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

pluggable indexing subsystem, by default Apache Lucene

SQL

Support of SQL

SQL for querying

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
Clojure
Elixir
Go
Groovy
Haskell
Java
JavaScript
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

yes

User defined Procedures and Functions

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

via event handler

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Sharding

Implicit feature of the cloud service

yes using Neo4j Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

none

yes

Implicit feature of the cloud service

Causal Clustering using Raft protocol

available in in Enterprise Version only

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Causal and Eventual Consistency configurable in Causal Cluster setup
Immediate Consistency in stand-alone mode

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

atomic operations within a document possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users can be defined per database

a simple user-level security was built in till version Access 2003

Access rights can be defined down to the item level

Users, roles and permissions. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

More information provided by the system vendor

Specific characteristics

Neo4j delivers graph technology that has been battle tested for performance and scale...
» more

Competitive advantages

Neo4j is the market leader, graph database category creator, and the most widely...
» more

Typical application scenarios

Real-Time Recommendations Master Data Management Identity and Access Management Network...
» more

Key customers

Over 800 commercial customers and over 4300 startups use Neo4j. Flagship customers...
» more

Market metrics

Neo4j boasts the world's largest graph database ecosystem with more than 140 million...
» more

Licensing and pricing models

GPL v3 license that can be used all the places where you might use MySQL. Neo4j Commercial...
» more

News

Announcing NODES 2024: Submit Your Talk
17 April 2024

ISO GQL: A Defining Moment in the History of Database Innovation
17 April 2024

This Week in Neo4j: Podcast, RAG, Neo4j Guide, ERP and more
13 April 2024

Neo4j Brings GraphRAG Capabilities for GenAI to Google Cloud
9 April 2024

Neo4j Is Now SOC2 Type 2 Compliant
8 April 2024

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.