DBMS > Atos Standard Common Repository vs. GeoSpock vs. Oracle Berkeley DB vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. GeoSpock vs. Oracle Berkeley DB vs. SpatiaLite

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

Widely used in-process key-value store

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Spatial DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

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

geospock.com

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

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Atos Convergence Creators

GeoSpock

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Alessandro Furieri

Initial release

2016

1994

2008

Current release

1703

2.0, September 2019

18.1.40, May 2020

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

Java, Javascript

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

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

only with the Berkeley DB XML edition

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

LDAP

JDBC

Supported programming languages

All languages with LDAP bindings

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

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

Access rights for users can be defined per table

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

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

GeoSpock's extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

provided by Google News

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, HPCwire

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

Motorola A780 Linux based smartphone to have mobile database
14 September 2004, Geekzone

provided by Google News

Share this page