DBMS > Atos Standard Common Repository vs. GeoSpock vs. SAP HANA vs. Solr

System Properties Comparison Atos Standard Common Repository vs. GeoSpock vs. SAP HANA vs. Solr

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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

In-memory, column based data store. Available as appliance or cloud service

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

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

geospock.com

www.sap.com/products/hana.html

solr.apache.org

Technical documentation

help.sap.com/hana

solr.apache.org/resources.html

Developer

Atos Convergence Creators

GeoSpock

SAP

Apache Software Foundation

Initial release

2016

2010

2006

Current release

1703

2.0, September 2019

2.0 SPS07 (April 4, 2023), April 2023

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, Javascript

Java

Server operating systems

Linux

hosted

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

Schema and schema-less with LDAP views

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

optional

yes

supports customizable data types and automatic typing

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

temporal, categorical

yes

All search fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

Solr Parallel SQL Interface

APIs and other access methods

LDAP

JDBC

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

SQLScript, R

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual 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

optimistic locking

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

Access rights for users can be defined per table

yes

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.