Hybrid storage engine for geospatial data using NoSQL and SQL paradigms

Citations Over Time

Abstract

The design and implementation of services to handle geospatial data involves thinking about storage engine performance and optimization for the desired use. NoSQL and relational databases bring their own advantages; therefore, it is necessary to choose one of these options according to the requirements of the solution. These requirements can change, or some operations may be performed in a more efficient way on another database engine, so using just one engine means being tied to its features and work model. This paper presents a hybrid approach (NoSQL-SQL) to store geospatial data on MongoDB, which are replicated and mapped on a PostgreSQL database, using an open source tool called ToroDB Stampede; solutions then can take advantage from either NoSQL or SQL features, to satisfy most of the requirements associated to the storage engine performance. A descriptive analysis to explain the workflow of the replication and synchronization in both engines precedes the quantitative analysis by which it was possible to determine that a normal database in PostgreSQL has a shorter response time than to perform the query in PostgreSQL with the hybrid database. In addition, the type of geometry increases the update response time of a materialized view.

Related Papers

• → State-of-the-Art Geospatial Information Processing in NoSQL Databases(2020)53 cited
• → A Study on Data Input and Output Performance Comparison of MongoDB and PostgreSQL in the Big Data Environment(2015)61 cited
• → When Relational-Based Applications Go to NoSQL Databases: A Survey(2019)12 cited
• NoSQL storage and management of geospatial data with emphasis onserving geospatial data using standard geospatial web services(2013)
• → A COMPARISON BETWEEN NOSQL AND RDBMS: STORAGE AND RETRIEVAL(2022)2 cited