Difference between Aerospike and AllegroGraph

1. Aerospike :
The Aerospike is a flash-optimized in-memory open-source NoSQL database and named after the eponymous company that produces it. It is a key-value data store designed to deliver sub-millisecond response time for real-time big data applications. The three main components of Aerospike are Aerospike Database Server, Aerospike Smart Clients and Aerospike Management Console.

2. AllegroGraph :
The AllegroGraph is a high performance, persistent RDF store with additional support for Graph DBMS. It operates as a Document Store designed for storing, retrieving and managing document-oriented information, in JSON-LD format. The first version of AllegroGraph was release in 2004.


Difference between Aerospike and AllegroGraph :

S.NO.	AEROSPIKE	ALLEGROGRAPH
1.	It was developed By Aerospike in 2012.	It was developed By Franz Inc. in 2004.
2.	It is a flash-optimized in-memory NoSQL database.	It is a high performance, persistent RDF store with additional support for Graph DBMS.
3.	The license of Aerospike is open-source.	The license of AllegroGraph is commercial.
4.	Server operating system for Aerospike is Linux.	Server operating systems for AllegroGraph are linux, OS X and Windows.
5.	It does not support XML Format.	It also does not support XML Format.
6.	It has user defined functions for Server-side scripting.	It supports the Server-side scripting with JavaScript or Common Lisp.
7.	Supported partitioning method is Sharding.	The partitioning can be done with Federation.
8.	It does not support SQL query language.	It uses SPARQL as query language.
9.	It supports only one replication method : Selectable Replication Factor.	It supports two replication methods : Master-Slave Replication and Multi-Master Replication.
10.	Aerospike does not provide the concept of Referential Integrity. Hence, no Foreign Keys.	AllegroGraph also does not provide the concept of Referential Integrity. Hence, no Foreign Keys.
11.	It supports in-memory capabilities.	It does not support in-memory capabilities.
12.	It offers an API for user-defined Map/Reduce methods.	It does not offer any API for user-defined Map/Reduce methods.
13.	It only supports atomic execution of operations.	It supports ACID properties.
14.	It’s primary database model is Key-Value Store.	It’s primary database models are Document Store, Graph DBMS and RDF Store.