DBMS > DataFS vs. Google BigQuery vs. TimesTen vs. Vitess

System Properties Comparison DataFS vs. Google BigQuery vs. TimesTen vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Large scale data warehouse service with append-only tables

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Object oriented DBMS

Relational DBMS

Secondary database models

Graph DBMS

Document store
Spatial DBMS

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

Score	0.02
Rank	#369	Overall
	#18	Object oriented DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

newdatabase.com

cloud.google.com/bigquery

www.oracle.com/database/technologies/related/timesten.html

vitess.io

Technical documentation

dev.mobiland.com/Overview.xsp

cloud.google.com/bigquery/docs

docs.oracle.com/en/database/other-databases/timesten/index.html

vitess.io/docs

Developer

Mobiland AG

Google

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

The Linux Foundation, PlanetScale

Initial release

2018

2010

1998

2013

Current release

1.1.263, October 2022

Release 22.1

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

Server operating systems

Windows

hosted

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Docker
Linux
macOS

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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

with proprietary extensions

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

RESTful HTTP/JSON API

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C#
C++
VB.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Java
Node.js
PL/SQL
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL

yes

proprietary syntax

Triggers

no, except callback-events from server when changes happened

yes

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

Windows-Profile

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

Users with fine-grained authorization concept

no user groups or roles

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.