DBMS > Google BigQuery vs. IBM Db2 Event Store vs. SingleStore

System Properties Comparison Google BigQuery vs. IBM Db2 Event Store vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Distributed Event Store optimized for Internet of Things use cases

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	5.38
Rank	#62	Overall
	#35	Relational DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/db2-event-store

www.singlestore.com

Technical documentation

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2-event-store

docs.singlestore.com

Developer

Google

IBM

SingleStore Inc.

Initial release

2010

2017

2013

Current release

2.0

8.5, January 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

free developer edition 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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C and C++

C++, Go

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

Linux

64 bit version required

Data scheme

yes

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

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

but no triggers and foreign keys

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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)

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» 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.