
In data migration between different types of NoSQL databases, data may not be directly transferred to the targeted database compared to migration of data between the same types of database. This is due to the heterogeneity of the storage paradigm of the NoSQL databases. For example, when migrating data from a document-oriented database such as MongoDB, which stores data in JSON (Java Object Notation) format to Neo4j, a graph-oriented database stores data in nodes, the differences among these databases’ storage paradigms require different representations of the data model in the targeted graph-oriented database. This paper proposed a sequential approach to migrate data from MongoDB to Neo4j. The approach migrates MongoDB data to Neo4j and verifies the migrated data using a comparative method. The paper discusses the migration algorithm and how complex fields in MongoDB, such as nested documents, are presented in Neo4j.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
