DBMS > Amazon SimpleDB vs. Blazegraph vs. Geode vs. SQLite

System Properties Comparison Amazon SimpleDB vs. Blazegraph vs. Geode vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.88
Rank	#133	Overall
	#23	Key-value stores

Score	0.81
Rank	#213	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/simpledb

blazegraph.com

geode.apache.org

www.sqlite.org

Technical documentation

docs.aws.amazon.com/simpledb

wiki.blazegraph.com

geode.apache.org/docs

www.sqlite.org/docs.html

Developer

Amazon

Blazegraph

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Dwayne Richard Hipp

Initial release

2007

2006

2002

2000

Current release

2.1.5, March 2019

1.1, February 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

RDF literal types

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.

Secondary indexes

yes

All columns are indexed automatically

yes

SQL

Support of SQL

SPARQL is used as query language

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
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

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

Concurrent data updates can be detected by the application

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

Access rights per client and object definable

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.