DBMS > Amazon Neptune vs. Dolt vs. Infobright vs. Yanza

System Properties Comparison Amazon Neptune vs. Dolt vs. Infobright vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Fast, reliable graph database built for the cloud

A MySQL compatible DBMS with Git-like versioning of data and schema

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Time Series DBMS for IoT Applications

Primary database model

Graph DBMS
RDF store

Relational DBMS

Time Series DBMS

Secondary database models

Document store

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

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Website

aws.amazon.com/neptune

github.com/dolthub/dolt
www.dolthub.com

ignitetech.com/softwarelibrary/infobrightdb

yanza.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.dolthub.com

Developer

Amazon

DoltHub Inc

Ignite Technologies Inc.; formerly InfoBright Inc.

Yanza

Initial release

2017

2018

2005

2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

hosted

Linux
macOS
Windows

Linux
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC

HTTP API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

currently in alpha release

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

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.

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

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.

yes

User concepts

Access control

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

Recent citations in the news

Exploring new features of Apache TinkerPop 3.7.x in Amazon Neptune | Amazon Web Services
7 June 2024, AWS Blog

Building NHM London's Planetary Knowledge Base with Amazon Neptune and the Registry of Open Data on AWS ...
5 June 2024, AWS Blog

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune | Amazon Web Services
3 June 2024, AWS Blog

AWS Weekly Roundup: LlamaIndex support for Amazon Neptune, force AWS CloudFormation stack deletion, and more ...
27 May 2024, AWS Blog

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

provided by Google News

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Radar Trends to Watch: July 2022 – O'Reilly
5 July 2022, O'Reilly Media

provided by Google News

Share this page