DBMS > EsgynDB vs. GeoMesa vs. Spark SQL
System Properties Comparison EsgynDB vs. GeoMesa vs. Spark SQL
Please select another system to include it in the comparison.
|Editorial information provided by DB-Engines|
|Name||EsgynDB Xexclude from comparison||GeoMesa Xexclude from comparison||Spark SQL Xexclude from comparison|
|Description||Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion||GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.||Spark SQL is a component on top of 'Spark Core' for structured data processing|
|Primary database model||Relational DBMS||Spatial DBMS||Relational DBMS|
|Developer||Esgyn||CCRi and others||Apache Software Foundation|
|Current release||4.0.4, October 2023||3.5.0 ( 2.13), September 2023|
|License Commercial or Open Source||commercial||Open Source Apache License 2.0||Open Source Apache 2.0|
|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||C++, Java||Scala||Scala|
|Server operating systems||Linux||Linux|
|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|
|SQL Support of SQL||yes||no||SQL-like DML and DDL statements|
|APIs and other access methods||ADO.NET|
|Supported programming languages||All languages supporting JDBC/ODBC/ADO.Net||Java|
|Server-side scripts Stored procedures||Java Stored Procedures||no||no|
|Partitioning methods Methods for storing different data on different nodes||Sharding||depending on storage layer||yes, utilizing Spark Core|
|Replication methods Methods for redundantly storing data on multiple nodes||Multi-source replication between multi datacenters||depending on storage layer||none|
|MapReduce Offers an API for user-defined Map/Reduce methods||yes||yes|
|Consistency concepts Methods to ensure consistency in a distributed system||Immediate Consistency||depending on storage layer|
|Foreign keys Referential integrity||yes||no||no|
|Transaction concepts Support to ensure data integrity after non-atomic manipulations of data||ACID||no||no|
|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.||no||depending on storage layer||no|
|User concepts Access control||fine grained access rights according to SQL-standard||yes depending on the DBMS used for storage||no|
More information provided by the system vendor
We invite representatives of system vendors to contact us for updating and extending the system information,
Related products and services
We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
|DB-Engines blog posts|
|Recent citations in the news|
Intel Granulate Optimizes Databricks' Data Management Operations
How Big Data Is Saving Lives in Real Time: IoV Data Analytics ...
Azure Data Engineer at In4group
Google-NVIDIA Partnership: Everything You Need To Know
Java or Python: Which One is Better for Data Science?
provided by Google News
Tech Lead, Data Engine
Data Scientist (L5) - Infrastructure Experimentation
Machine Learning Associate, 2024 Graduate U.S.
Senior Backline Engineer - Spark
Python/Spark/SQL Data Egnineer
Share this page