GitHub user imbajin edited a comment on the discussion: Few question regarding hugegraph
> I recently got to know about Hugegraph and i am very impressed with its > features like API, multi DB support, backup & rollback, AI support. But one > thing that surprise me why this isnt popular? I saw one discussion where few > company has posted that they use this DB. My question is > > 1. Does this db really support 100B data as mentioned on website? > 2. What is the latest future plan? > 3. Is there any recent real world deployment of this DB in production? Thank you for your attention. Some context for it: You can understand it as a new version of JG that was originally designed as a **data structure** rewrite and comprehensive enhancement. Later, it gradually evolved into its own independently managed `RocksDB+Raft` PD/storage system, and made significant improvements in many engineering areas. (Include Graph Computing/Toolchain/AI.. etc, not only a graph-db:) > You may wonder, since it has undergone so many optimizations and improvements > and provided a relatively complete surrounding > ecosystem, why isn't it popular enough? The main issue is that it lacks community operations people/skills, The field of graphics is relatively niche and has a high threshold. Even if you can provide better engineering practices and designs than Neo4j and JG, you still need a lot of energy to make ordinary people believe in it, and a lot of energy to do productization/documentation/blog related work.(Also lacks various official blogs, source code analysis, best practices, and more) So indeed, the community lacks devs who are willing to participate and further promote it, whether it is in terms of code or documentation. We are also willing to guide everyone in our personal time > 1. Does this db really support 100B data as mentioned on website? Of course, if you know about `HBase` and `Cassandra`, they can support more than 100B of data stably. It's just a matter of optimizing read and write performance. Simply storing data is not difficult, the challenge is to **read them efficiently**, which is why we later introduced a distributed version of our home-grown `Raft + RocksDB` that no longer relies on external storage. > 2. What is the latest future plan? refer https://github.com/apache/incubator-hugegraph/issues/2724 & https://github.com/apache/incubator-hugegraph/milestones <img width="723" alt="image" src="https://github.com/user-attachments/assets/4d94b521-160a-477d-9435-ba227d83e6cf"; /> The other one is graduating from the Apache Incubator > 3. Is there any recent real world deployment of this DB in production? Yes, most of our existing PMC/Committers members are actual users (others parts in the user-case issue) GitHub link: https://github.com/apache/incubator-hugegraph/discussions/2737#discussioncomment-12297155 ---- This is an automatically sent email for dev@hugegraph.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@hugegraph.apache.org
