DBMS > atoti vs. Google Cloud Datastore vs. Linter vs. TimesTen

System Properties Comparison atoti vs. Google Cloud Datastore vs. Linter vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDBMS for high security requirements

In-Memory RDBMS compatible to Oracle

Primary database model

Object oriented DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

atoti.io

cloud.google.com/datastore

linter.ru

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

Technical documentation

docs.atoti.io

cloud.google.com/datastore/docs

docs.oracle.com/database/timesten-18.1

Developer

ActiveViam

Google

relex.ru

Oracle, TimesTen Performance Software, HP

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

Initial release

2008

1990

1998

Current release

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

free versions available

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

Java

C and C++

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

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

Multidimensional Expressions (MDX)

SQL-like query language (GQL)

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

Python

using Google App Engine

yes

proprietary syntax with the possibility to convert from PL/SQL

PL/SQL

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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)

fine grained access rights according to SQL-standard

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

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google News

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Best cloud storage of 2024
29 April 2024, TechRadar

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

provided by Google News

Oracle starts peddling Exalytics in-memory appliance
12 March 2012, The Register

provided by Google News

Share this page