DBMS > Atos Standard Common Repository vs. SpaceTime vs. Sphinx vs. Warp 10 vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. SpaceTime vs. Sphinx vs. Warp 10 vs. Yaacomo

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.

Open source search engine for searching in data from different sources, e.g. relational databases

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

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

Primary database model

Document store
Key-value store

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	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

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

www.mireo.com/spacetime

sphinxsearch.com

www.warp10.io

yaacomo.com

Technical documentation

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Atos Convergence Creators

Mireo

Sphinx Technologies Inc.

SenX

Q2WEB GmbH

Initial release

2016

2020

2001

2015

2009

Current release

1703

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 2.0

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

Java

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

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

full-text index on all search fields

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

SQL-like query language (SphinxQL)

yes

APIs and other access methods

LDAP

RESTful HTTP API

Proprietary protocol

HTTP API
Jupyter
WebSocket

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C#
C++
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Fixed-grid hypercubes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Real-time block device replication (DRBD)

none

selectable replication factor

based on HBase

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

based on HBase

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

The original contents of fields are not stored in the Sphinx index.

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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

DB-Engines blog posts

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Googles Newest Challenger
11 January 2024, Free Press Journal

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018 | WQXR Editorial
22 December 2018, WQXR Radio

provided by Google News

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

Time Series Intelligence Software Market Analysis and Revenue Prediction | Azure Time Series Insights, Trendalyze ...
20 May 2024, Weekly Post Gazette

provided by Google News

Share this page