DBMS > EventStoreDB vs. Google BigQuery vs. searchxml vs. YottaDB

System Properties Comparison EventStoreDB vs. Google BigQuery vs. searchxml vs. YottaDB

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.

Large scale data warehouse service with append-only tables

DBMS for structured and unstructured content wrapped with an application server

A fast and solid embedded Key-value store

Primary database model

Event Store

Relational DBMS

Native XML DBMS
Search engine

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.eventstore.com

cloud.google.com/bigquery

www.searchxml.net/category/products

yottadb.com

Technical documentation

developers.eventstore.com

cloud.google.com/bigquery/docs

www.searchxml.net/support/handouts

yottadb.com/resources/documentation

Developer

Event Store Limited

Google

informationpartners gmbh

YottaDB, LLC

Initial release

2012

2010

2015

2001

Current release

21.2, February 2021

1.0

License

Commercial or Open Source

Open Source

commercial

Open Source

AGPL 3.0

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

Server operating systems

Linux
Windows

hosted

Windows

Docker
Linux

Data scheme

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

most other programming languages supported via APIs

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

on the application server

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

yes

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

Transaction concepts

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

Since BigQuery is designed for querying data

multiple readers, single writer

optimistic locking

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.

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

Users and groups based on OS-security mechanisms

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.