DBMS > Amazon Neptune vs. Apache Drill vs. Manticore Search vs. SAP SQL Anywhere vs. SQLite

System Properties Comparison Amazon Neptune vs. Apache Drill vs. Manticore Search vs. SAP SQL Anywhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
RDF store

Document store
Relational DBMS

Search engine

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	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/neptune

drill.apache.org

manticoresearch.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

Technical documentation

aws.amazon.com/neptune/developer-resources

drill.apache.org/docs

manual.manticoresearch.com

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

Developer

Amazon

Apache Software Foundation

Manticore Software

SAP

formerly Sybase

Dwayne Richard Hipp

Initial release

2017

2012

2017

1992

2000

Current release

1.20.3, January 2023

6.0, February 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPL version 2

commercial

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

C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Data scheme

schema-free

Fixed schema

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

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC
RESTful HTTP API

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

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C++

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Synchronous replication based on Galera library

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

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

with encyption-at-rest

Depending on the underlying data source

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.

Depending on the underlying data source

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Depending on the underlying data source

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.