DBMS > GeoMesa vs. Sadas Engine vs. VelocityDB

System Properties Comparison GeoMesa vs. Sadas Engine vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	GeoMesa  Xexclude from comparison	Sadas Engine  Xexclude from comparison	VelocityDB  Xexclude from comparison
Description	GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.	SADAS Engine is a columnar DBMS specifically designed for high performance in Data warehouse environments	A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)
Primary database model	Spatial DBMS	Relational DBMS	Graph DBMS Object oriented DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 0.75 Rank #204   Overall #3   Spatial DBMS	Score 0.00 Rank #356   Overall #155   Relational DBMS	Score 0.02 Rank #341   Overall #35   Graph DBMS #17   Object oriented DBMS
Website	www.geomesa.org	www.sadasengine.com	velocitydb.com
Technical documentation	www.geomesa.org/­documentation/­stable/­user/­index.html	www.sadasengine.com/­index.php/­downloads/­documentation-columnar-db	velocitydb.com/­UserGuide
Developer	CCRi and others	SADAS s.r.l.	VelocityDB Inc
Initial release	2014	2006	2011
Current release	3.2.0, April 2021	8.0	7.x
License Commercial or Open Source	Open Source Apache License 2.0	commercial free trial version available	commercial
Cloud-based only Only available as a cloud service	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Scala	C++	C#
Server operating systems		AIX Linux Windows	Any that supports .NET
Data scheme	yes	yes	yes
Typing predefined data types such as float or date	yes	yes	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.	no	no	no
Secondary indexes	yes	yes	yes
SQL Support of SQL	no	yes	no
APIs and other access methods		JDBC ODBC Proprietary protocol	.Net
Supported programming languages		.Net C C# C++ Groovy Java PHP Python	.Net
Server-side scripts Stored procedures	no	no	no
Triggers	no	no	Callbacks are triggered when data changes
Partitioning methods Methods for storing different data on different nodes	depending on storage layer	horizontal partitioning	Sharding
Replication methods Methods for redundantly storing data on multiple nodes	depending on storage layer	none
MapReduce Offers an API for user-defined Map/Reduce methods	yes	no	no
Consistency concepts Methods to ensure consistency in a distributed system	depending on storage layer	Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	no	yes	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	no		ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes	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 managed by 'Learn by Usage'	yes
User concepts Access control	yes depending on the DBMS used for storage	Access rights for users, groups and roles according to SQL-standard	Based on Windows Authentication
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
	GeoMesa	Sadas Engine	VelocityDB
DB-Engines blog posts	Spatial database management systems 6 April 2021, Matthias Gelbmann show all