DB-EnginesInfluxDB: Focus on building software with an easy-to-use serverless, scalable time series platformEnglish
Deutsch
Knowledge Base of Relational and NoSQL Database Management Systemsprovided by solid IT

DBMS > GeoMesa vs. Kinetica vs. RethinkDB

System Properties Comparison GeoMesa vs. Kinetica vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
NameGeoMesa  Xexclude from comparisonKinetica  Xexclude from comparisonRethinkDB  Xexclude from comparison
DescriptionGeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.Fully vectorized database across both GPUs and CPUsDBMS for the Web with a mechanism to push updated query results to applications in realtime.
Primary database modelSpatial DBMSRelational DBMSDocument store
Secondary database modelsSpatial DBMS
DB-Engines Ranking infomeasures the popularity of database management systemsranking trend
Trend Chart
Score0.75
Rank#203  Overall
#3  Spatial DBMS
Score0.64
Rank#218  Overall
#106  Relational DBMS
Score3.06
Rank#101  Overall
#19  Document stores
Websitewww.geomesa.orgwww.kinetica.comrethinkdb.com
Technical documentationwww.geomesa.org/­documentation/­stable/­user/­index.htmlwww.kinetica.com/­docsrethinkdb.com/­docs
DeveloperCCRi and othersKineticaThe Linux Foundation infosince July 2017
Initial release201420122009
Current release3.2.0, April 20217.1, August 20212.4.1, August 2020
License infoCommercial or Open SourceOpen Source infoApache License 2.0commercialOpen Source infoApache Version 2
Cloud-based only infoOnly available as a cloud servicenonono
DBaaS offerings (sponsored links) infoDatabase as a Service

Providers of DBaaS offerings, please contact us to be listed.
Implementation languageScalaC, C++C++
Server operating systemsLinuxLinux
OS X
Windows
Data schemeyesyesschema-free
Typing infopredefined data types such as float or dateyesyesyes infostring, binary, float, bool, date, geometry
XML support infoSome form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.nonono
Secondary indexesyesyesyes
SQL infoSupport of SQLnoSQL-like DML and DDL statementsno
APIs and other access methodsJDBC
ODBC
RESTful HTTP API
Supported programming languagesC++
Java
JavaScript (Node.js)
Python
C infocommunity-supported driver
C# infocommunity-supported driver
C++ infocommunity-supported driver
Clojure infocommunity-supported driver
Dart infocommunity-supported driver
Erlang infocommunity-supported driver
Go infocommunity-supported driver
Haskell infocommunity-supported driver
Java infoofficial driver
JavaScript (Node.js) infoofficial driver
Lisp infocommunity-supported driver
Lua infocommunity-supported driver
Objective-C infocommunity-supported driver
Perl infocommunity-supported driver
PHP infocommunity-supported driver
Python infoofficial driver
Ruby infoofficial driver
Scala infocommunity-supported driver
Server-side scripts infoStored proceduresnouser defined functions
Triggersnoyes infotriggers when inserted values for one or more columns fall within a specified rangeClient-side triggers through changefeeds
Partitioning methods infoMethods for storing different data on different nodesdepending on storage layerShardingSharding inforange based
Replication methods infoMethods for redundantly storing data on multiple nodesdepending on storage layerSource-replica replicationSource-replica replication
MapReduce infoOffers an API for user-defined Map/Reduce methodsyesnoyes
Consistency concepts infoMethods to ensure consistency in a distributed systemdepending on storage layerImmediate Consistency or Eventual Consistency depending on configurationImmediate Consistency
Foreign keys infoReferential integritynoyesno
Transaction concepts infoSupport to ensure data integrity after non-atomic manipulations of datanonoAtomic single-document operations
Concurrency infoSupport for concurrent manipulation of datayesyesyes infoMVCC based
Durability infoSupport for making data persistentyesyesyes
In-memory capabilities infoIs there an option to define some or all structures to be held in-memory only.depending on storage layeryes infoGPU vRAM or System RAMno
User concepts infoAccess controlyes infodepending on the DBMS used for storageAccess rights for users and roles on table levelyes infousers and table-level permissions
More information provided by the system vendor
GeoMesaKineticaRethinkDB
Specific characteristicsNative and fully vectorized database across both GPUs and CPUs, with memory first...
» more
Competitive advantagesBest in class geospatial and temporal analytics. Lockless architecture provides real-time...
» more
Typical application scenariosAny application requiring (1) real time insights, (2) time series analysis (3) geospatial...
» more
Key customersCitibank, US Air Force, Softbank, OVO, Telkomsel, USPS, 2 of the top 3 US Telcos,...
» more
Market metricsThe largest IoT deployment in the world, NORAD, runs on Kinetica.
» more
Licensing and pricing modelsAlways Free Tier in the Cloud, Pay-As-You-Go Consumption Based Pricing, and Portable...
» more

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
GeoMesaKineticaRethinkDB
DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all