DBMS > Amazon Neptune vs. GeoMesa vs. IRONdb vs. Tkrzw

System Properties Comparison Amazon Neptune vs. GeoMesa vs. IRONdb vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, reliable graph database built for the cloud

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

aws.amazon.com/neptune

www.geomesa.org

www.circonus.com/solutions/time-series-database/

dbmx.net/tkrzw

Technical documentation

aws.amazon.com/neptune/developer-resources

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

docs.circonus.com/irondb/category/getting-started

Developer

Amazon

CCRi and others

Circonus LLC.

Mikio Hirabayashi

Initial release

2017

2014

2017

2020

Current release

5.0.1, July 2024

V0.10.20, January 2018

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

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

Scala

C and C++

C++

Server operating systems

hosted

Linux

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

HTTP API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes, in Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Automatic, metric affinity per node

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.

depending on storage layer

configurable replication factor, datacenter aware

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

In-memory capabilities

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

depending on storage layer

yes

using specific database classes

User concepts

Access control

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

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

Recent citations in the news

How Amazon stores deliver trustworthy shopping and seller experiences using Amazon Neptune
18 September 2024, AWS Blog

How Prisma Cloud built Infinity Graph using Amazon Neptune and Amazon OpenSearch Service
27 August 2024, AWS Blog

Hydrating the Natural History Museum’s Planetary Knowledge Base with Amazon Neptune and Open Data on AWS
13 September 2024, AWS Blog

Using knowledge graphs to build GraphRAG applications with Amazon Bedrock and Amazon Neptune
1 August 2024, AWS Blog

New Amazon Neptune engine version delivers up to 9 times faster and 10 times higher throughput for openCypher query performance
23 July 2024, AWS Blog

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

provided by Google News

Share this page