DBMS > GeoSpock vs. Manticore Search vs. OrientDB vs. SQLite

System Properties Comparison GeoSpock vs. Manticore Search vs. OrientDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Spatial and temporal data processing engine for extreme data scale

Multi-storage database for search, including full-text search.

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

manticoresearch.com

orientdb.org

www.sqlite.org

Technical documentation

manual.manticoresearch.com

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

Developer

GeoSpock

Manticore Software

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Initial release

2017

2010

2000

Current release

2.0, September 2019

6.0, February 2023

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache version 2

Open Source

Public Domain

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, Javascript

C++

Java

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

All OS with a Java JDK (>= JDK 6)

server-less

Data scheme

yes

Fixed schema

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

not rigid because of 'dynamic typing' concept.

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.

Can index from XML

Secondary indexes

temporal, categorical

yes

full-text index on all search fields

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore 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

Access rights for users can be defined per table

Access rights for users and roles; record level security configurable

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.