DBMS > Atos Standard Common Repository vs. SpaceTime vs. Transwarp Hippo vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. SpaceTime vs. Transwarp Hippo vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

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

Primary database model

Document store
Key-value store

Spatial DBMS

Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.mireo.com/spacetime

www.transwarp.cn/en/subproduct/hippo

yaacomo.com

Developer

Atos Convergence Creators

Mireo

Q2WEB GmbH

Initial release

2016

2020

2023

2009

Current release

1703

1.0, May 2023

License

Commercial or Open Source

commercial

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

Java

C++

Server operating systems

Linux

Linux
macOS

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

yes

Vector, Numeric and String

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.

yes

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

yes

APIs and other access methods

LDAP

RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C#
C++
Python

C++
Java
Python

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Fixed-grid hypercubes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Real-time block device replication (DRBD)

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 or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific 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

LDAP bind authentication

yes

Role based access control and fine grained access rights

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.

Share this page