DBMS > EventStoreDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SurrealDB

System Properties Comparison EventStoreDB vs. Microsoft Azure Cosmos DB vs. searchxml vs. SurrealDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Globally distributed, horizontally scalable, multi-model database service

DBMS for structured and unstructured content wrapped with an application server

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Event Store

Document store
Graph DBMS
Key-value store
Wide column store

Native XML DBMS
Search engine

Document store
Graph DBMS

Secondary database models

Spatial DBMS

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

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

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

www.eventstore.com

azure.microsoft.com/services/cosmos-db

www.searchxml.net/category/products

surrealdb.com

Technical documentation

developers.eventstore.com

learn.microsoft.com/azure/cosmos-db

www.searchxml.net/support/handouts

surrealdb.com/docs

Developer

Event Store Limited

Microsoft

informationpartners gmbh

SurrealDB Ltd

Initial release

2012

2014

2015

2022

Current release

21.2, February 2021

1.0

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

commercial

Open Source

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

Rust

Server operating systems

Linux
Windows

hosted

Windows

Linux
macOS
Windows

Data scheme

schema-free

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

RESTful HTTP API
WebDAV
XQuery
XSLT

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

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

C++

most other programming languages supported via APIs

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

JavaScript

yes

on the application server

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

Access rights can be defined down to the item level

Domain, group and role-based access control at the document level and for application services

yes, based on authentication and database rules

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.