DBMS > Atos Standard Common Repository vs. DolphinDB vs. GeoMesa vs. Sphinx

System Properties Comparison Atos Standard Common Repository vs. DolphinDB vs. GeoMesa vs. Sphinx

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.

Description

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

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Primary database model

Document store
Key-value store

Time Series DBMS

Spatial DBMS

Search engine

Secondary database models

Relational DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

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

www.dolphindb.com

www.geomesa.org

sphinxsearch.com

Technical documentation

docs.dolphindb.cn/en/help200/index.html

www.geomesa.org/documentation/stable/user/index.html

sphinxsearch.com/docs

Developer

Atos Convergence Creators

DolphinDB, Inc

CCRi and others

Sphinx Technologies Inc.

Initial release

2016

2018

2014

2001

Current release

1703

v2.00.4, January 2022

5.0.0, May 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

free community version available

Open Source

Apache License 2.0

Open Source

GPL version 2, commercial licence available

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

Scala

C++

Server operating systems

Linux

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

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

SQL

Support of SQL

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

LDAP

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

Proprietary protocol

Supported programming languages

All languages with LDAP bindings

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

depending on storage layer

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

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.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

depending on storage layer

User concepts

Access control

LDAP bind authentication

Administrators, Users, Groups

yes

depending on the DBMS used for storage

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

5 Powerful Alternatives to Elasticsearch
25 April 2024, Insider Monkey

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

Royal Mail stamp prices could rise, warns Czech Sphinx
3 June 2024, Proactive Investors UK

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

provided by Google News

Share this page