community
Pick of the Week at NebulaGraph - NebulaGraph DBaaS is Public for Beta Test
Normally the weekly issue covers NebulaGraph Updates and Community Q&As. If something major happens, it will also be covered in the additional Events of the Week section.
Events of the Week
- NebulaGraph DBaaS is public for beta test
The NebulaGraph DBaaS service is officially public for beta test this week. You are welcome to try it for free. Your need to submit a request to create an instance. After the submission, the support team will handle the request within two calendar days. Here is the entrance: https://cloud.nebula-graph.io/
- Sherman Ye, the CEO of vesoft inc. was interviewed by TNP
As the representative of the new generation graph database, NebulaGraph was invited to participate in the online database seminar hosted by TheNextPlatform, the famous technology media. The topic for this seminar is the new generation graph database. Sherman Ye， the founder and CEO of vesoft inc, was interviewed by editor-in-chief Timothy Prickett Morgan to discuss topics such as the design idea, the advantages of NebulaGraph, the market positioning of NebulaGraph, and the importance of the open source model to NebulaGraph. Check the interview on YouTube.
NebulaGraph Updates
The updates of Nebula in the last week:
• Support to configure the prefix bloom filter for the RocksDB. Improved the query performance for QueryEdgeProps and QueryVertexProps and decreased the memory usage for the bloom filter. For more information, check this pull request: https://github.com/vesoft-inc/nebula/pull/2274
• Fixed the bug that may cause the newly-added column prop crash in LOOKUP ON after alter add column. For more information, check this pull request: https://github.com/vesoft-inc/nebula/pull/2341
• Refactored the RAFT leader election logic. For more information, check this pull request: https://github.com/vesoft-inc/nebula/pull/2327
Community Q&A
The community Q&A topic for the last week is about index, cache, and search engine.
Q: How is the index created in NebulaGraph? For query efficiency, is it necessary to build a layer of Redis cache above the query interface layer? And it is necessary to introduce search engines such as Solr and ElasticSearch?
Nebula: Good question. I will answer them one by one.
How is the index created in NebulaGraph?
Regarding the index storage, you can refer to this article: How Indexing Works in NebulaGraph. In addition, the index and data are stored in the same partition so that retrieving data is more easily in the partition by using the index and no network transmission is needed across different partitions.
For query efficiency, is it necessary to build a layer of Redis cache above the query interface layer?
I personally think a Redis cache is only needed in the OLAP. Because data changes a lot in OLTP, the cache will only add extra load. At present, NebulaGraph introduced the LRU cache mechanism to its storage service, so I think it's more convenient if we put the cache here. Of course, if you don't require high data accuracy and you can accept some data latency, you may still need the cache layer. One thing to add, when introducing a cache layer, you need to think about whether a third party system (e.g. Redis) can be used.
Is it necessary to introduce search engines such as Solr and ElasticSearch?
I think this is a reasonable requirement. Actually, we are planning to support a third party full text search engine to strengthen fuzzy matching, wildcard matching, regular expression matching, prefix matching, suffix matching, and so on.
