DBMS > BigObject vs. Graph Engine vs. TimescaleDB vs. YottaDB

System Properties Comparison BigObject vs. Graph Engine vs. TimescaleDB vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Graph DBMS
Key-value store

Time Series DBMS

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	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

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

Website

Technical documentation

docs.bigobject.io

www.graphengine.io/docs/manual

docs.timescale.com

yottadb.com/resources/documentation

Developer

BigObject, Inc.

Microsoft

Timescale

YottaDB, LLC

Initial release

2015

2010

2017

2001

Current release

2.15.0, May 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

MIT License

Open Source

Apache 2.0

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

.NET

Linux
OS X
Windows

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL-like DML and DDL statements

yes

full PostgreSQL SQL syntax

by using the Octo plugin

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

Lua

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with hot standby and reads on replicas

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

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.

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

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019 - DataScienceCentral.com
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page