Table of contents
The sub-database and sub-table of the graph database:
Take Neo4j Desktop as an example:
neo4j Desktop page hierarchy:
Divided into three levels:
- Project: used to distinguish multiple projects
- DBMS: There can be multiple versions of DBMS in a project
- database: There can be multiple databases in one DBMS
Graph database export:
Select a database, click on the right side , and click dump to export the database file to the current directory. After exporting, you can see it below:
Graph database import:
Copy the exported .dump file to the project directory to be imported:
Click Import dump into existing DMBS, select a DMBS, and create a new database to complete the import.
The sub-database and sub-table of the graph database:
The purpose of sub-database and sub-table is to solve the performance problem caused by the large amount of data. By dividing data into multiple database instances or dispersing into multiple data tables, the load of a single database instance or data table can be reduced, and the processing capacity and performance of the database can be improved.
Graph databases do not involve the concept of traditional db sub-database and table. Graph databases focus on the topology of the graph and the relationship between nodes. Indexes and efficient traversal algorithms are usually used to speed up query performance, rather than sub-databases and tables. You can also use a distributed framework to distribute data to multiple server nodes, and use partitioning algorithms to manage the distribution of data and the routing of query operations to achieve high availability.