DBMS > Google Cloud Bigtable vs. IRONdb vs. ObjectBox vs. Yaacomo

System Properties Comparison Google Cloud Bigtable vs. IRONdb vs. ObjectBox vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Extremely fast embedded database for small devices, IoT and Mobile

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Key-value store
Wide column store

Time Series DBMS

Object oriented DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Website

cloud.google.com/bigtable

www.circonus.com/solutions/time-series-database/

objectbox.io

yaacomo.com

Technical documentation

cloud.google.com/bigtable/docs

docs.circonus.com/irondb/category/getting-started

docs.objectbox.io

Developer

Google

Circonus LLC.

ObjectBox Limited

Q2WEB GmbH

Initial release

2015

2017

2009

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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

Server operating systems

hosted

Linux

Android
iOS
Linux
macOS
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HTTP API

Proprietary native API

JDBC
ODBC

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

Server-side scripts

Stored procedures

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

configurable replication factor, datacenter aware

online/offline synchronization between client and server

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

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.

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

fine grained access rights according to SQL-standard

More information provided by the system vendor

News

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google announces Axion, its first Arm-based CPU for data centers
9 April 2024, Yahoo Movies Canada

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Industrial IoT (IIoT) edge solution for railway operators – a Kapsch ObjectBox Case Study
21 June 2019, 1E9

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

Share this page