This document outlines the future development plans for TuGraph, including features currently under development, those not in the development pipeline, and completed functionalities not included in the open-source version.
TuGraph aims to be an open-source, high-performance graph database. It adopts a centralized storage approach for graph data and, in the short term, does not consider data sharding. Instead, it employs a master-slave replication mode to address high-concurrency read scenarios, while utilizing cloud-based storage solutions to address storage capacity challenges.
TuGraph was open-sourced on September 1, 2022, and has received regular bug fixes and enhancements based on community feedback.
| Version | Functionality | Date |
|---|---|---|
| 3.3.0 | Initial open-source release | 2022.9.1 |
| 3.3.1 | Refactored graph analysis engine with multi-mode support | 2022.10.14 |
| 3.3.2 | Added OGM support and improved unit test coverage | 2022.11.21 |
| 3.3.3 | Iterative improvements to link authentication mechanism and addition of English documentation | 2022.12.23 |
| 3.3.4 | Cloud deployment support and streamlined LDBC SNB Audit process | 2023.1.28 |
| 3.4.0 | Added support for OLAP Python API and upgraded offline data import | 2023.3.11 |
| 3.5.0 | Introduced POG (Procedures On Graph query language), frontend upgrades | 2023.6.5 |
| 3.5.1 | Added learning engine, Procedure Rust API, and storage-property separation | 2023.7.14 |
In addition, TuGraph has established a comprehensive quality system, including automated unit testing, integration testing, and performance testing.
The planned high availability feature was delayed in the first half of the year, while the graph learning capability was iterated earlier than scheduled. The second half of the year will focus on completing the high availability feature and being the first to support a pre-print version of ISO GQL.
| Version | Functionality | Planned Date | | 3.6.0 | High availability support | 2023.8 | | 4.0.0 | ISO GQL language support | 2023.10 |
In addition to the aforementioned core functionalities, the following components are planned for development in 2023.
| Version | Functionality | Planned Date |
|---|---|---|
| 3.5.x | Optimization of the logging system | 2023.7 |
| 3.5.x | Cold backup support | 2023.9 |
| 3.5.x | Support for edge upsert import | 2023.9 |
| x.x.x | Trigger support exploration | 2023.12 |
| x.x.x | Exploring new storage engines | TBD |
| x.x.x | Rapid schema addition and deletion | TBD |
| x.x.x | TuGraph Browser version iteration | TBD |
| x.x.x | Iteration of stored procedure Python API | TBD |
Currently, the development team's resources are limited, and we cannot implement all the desired features for TuGraph. However, during the feature planning process, we have identified a range of ideas worth exploring. The team has conducted some initial exploration, and we welcome community collaboration in developing the following features:
| Version | Functionality | Planned Date |
|---|---|---|
| x.x.x | Documentation improvements | TBD |
| x.x.x | Enrichment of APOC tools | TBD |
| x.x.x | Support for default property values | TBD |
| x.x.x | Composite index for multiple properties | TBD |
| x.x.x | Online full import support | TBD |
| x.x.x | Enhanced graph permissions | TBD |
| x.x.x | NLP (Natural Language Processing) support | TBD |
| x.x.x | Java Procedure API | TBD |
| x.x.x | Rapid database migration | TBD |
| x.x.x | Spatiotemporal data support | TBD |
For simpler features, we will label them as "good first issue" on GitHub issues, and we welcome discussions from technology enthusiasts interested in graph databases.