GitHub user imbajin added a comment to the discussion: Few question regarding hugegraph
> In case of ≥ 1.5, if I use casssandra as back end, how a configuration will > look like, is there any scalable cassandra backed configuration available? In > production which is recommended back end storage for scaled HG, > Cassandra/Hbase/Hstore ? First, if you are using any backend other than 'HStore', version 1.5 will not be significantly different from previous versions. You can refer to the default Cassandra configuration in the previous documentation (performance optimization is a separate matter, but it doesn't need to be addressed too early). For the community, maintaining multiple backends is clearly costly. We recommend prioritizing backends that use Binary serialization (such as HBase/RocksDB). In the future, the community will significantly streamline unnecessary backends to reduce the difficulty of user selection. The core is to maintain the **Raft + RocksDB** combination (which can be single-node or distributed, and manages its own storage without any external component dependencies, making performance optimization and adjustment much easier). Otherwise, you will face a very large overhead in customizing and optimizing the performance of different backends (e.g., MySQL/ScyllaDB/HBase/Cassandra...). Version 1.5 is the last version in which we will maintain compatibility with all backends. Starting with the next version, 1.7, we will reduce the number of backends by 50%, and by version 2.0, we will only keep backends that use Binary serialization and remove the Backend abstraction layer (users who want to use a compatible version can continue to use 1.5). GitHub link: https://github.com/apache/incubator-hugegraph/discussions/2737#discussioncomment-12310286 ---- This is an automatically sent email for dev@hugegraph.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@hugegraph.apache.org
