DBMS > Amazon Neptune vs. Atos Standard Common Repository vs. OpenQM vs. SwayDB

System Properties Comparison Amazon Neptune vs. Atos Standard Common Repository vs. OpenQM vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Amazon Neptune  Xexclude from comparison	Atos Standard Common Repository  Xexclude from comparison	OpenQM also called QM  Xexclude from comparison	SwayDB  Xexclude from comparison
		This system has been discontinued and will be removed from the DB-Engines ranking.
Description	Fast, reliable graph database built for the cloud	Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks	QpenQM is a high-performance, self-tuning, multi-value DBMS	An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage
Primary database model	Graph DBMS RDF store	Document store Key-value store	Multivalue DBMS	Key-value 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 0.34 Rank #284   Overall #10   Multivalue DBMS	Score 0.04 Rank #387   Overall #61   Key-value stores
Website	aws.amazon.com/­neptune	atos.net/en/convergence-creators/portfolio/standard-common-repository	www.rocketsoftware.com/­products/­rocket-multivalue-application-development-platform/­rocket-open-qm	swaydb.simer.au
Technical documentation	aws.amazon.com/­neptune/­developer-resources
Developer	Amazon	Atos Convergence Creators	Rocket Software, originally Martin Phillips	Simer Plaha
Initial release	2017	2016	1993	2018
Current release		1703	3.4-12
License Commercial or Open Source	commercial	commercial	Open Source GPLv2, extended commercial license available	Open Source GNU Affero GPL V3.0
Cloud-based only Only available as a cloud service	yes	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language		Java		Scala
Server operating systems	hosted	Linux	AIX FreeBSD Linux macOS Raspberry Pi Solaris Windows
Data scheme	schema-free	Schema and schema-less with LDAP views	yes with some exceptions	schema-free
Typing predefined data types such as float or date	yes	optional		no
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.	no	yes	yes	no
Secondary indexes	no	yes	yes	no
SQL Support of SQL	no	no	no	no
APIs and other access methods	OpenCypher RDF 1.1 / SPARQL 1.1 TinkerPop Gremlin	LDAP
Supported programming languages	C# Go Java JavaScript PHP Python Ruby Scala	All languages with LDAP bindings	.Net Basic C Java Objective C PHP Python	Java Kotlin Scala
Server-side scripts Stored procedures	no	no	yes	no
Triggers	no	yes	yes	no
Partitioning methods Methods for storing different data on different nodes	none	Sharding cell division	yes	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.	yes	yes	none
MapReduce Offers an API for user-defined Map/Reduce methods	no		no	no
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency	Immediate Consistency or Eventual Consistency depending on configuration	Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	yes Relationships in graphs	no	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	ACID	Atomic execution of specific operations	ACID	Atomic execution of operations
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes with encyption-at-rest	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.		yes		yes
User concepts Access control	Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)	LDAP bind authentication	Access rights can be defined down to the item level	no
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
	Amazon Neptune	Atos Standard Common Repository	OpenQM also called QM	SwayDB
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 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 Amazon Neptune Analytics is now available in the AWS Europe (London) Region 14 March 2024, AWS Blog provided by Google News	Infographic: What makes a Mobile Operator's setup future proof? 10 February 2024, Atos provided by Google News

Share this page