We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(5)
ProfaneDB: http://profanedb.gitlab.io
“ProfaneDB 是 Protocol Buffers 和 RocksDB 之间的 gRPC 接口”
PS:
尽管这个问题是 10 年前提出的,但我仍然发现它非常相关,特别是随着 gRPC 的提升。希望能有所帮助。
ProfaneDB: http://profanedb.gitlab.io
"ProfaneDB is a gRPC interface between Protocol Buffers and RocksDB"
P.S:
Though the question was asked 10 years ago I still find it very relevant, specially with the ascension of gRPC. Hope that can be of help.
我不知道任何(不是说它们不存在,我只是不知道它们),但也许值得讨论替代策略以及利弊。
通常,您希望存储协议缓冲区的序列化版本,并通过某个特定键(也许是唯一标识符)进行索引。然后,您可以为指向该唯一标识符的其他有趣字段构建二级索引。这个想法是,您希望像这样的显式索引能够扩展到超出提供任意索引的系统的范围。这显然开启了一个充满新问题的世界(例如陈旧的任意索引)。
I am not aware of any (not that they don't exist, I just don't know about them), but perhaps it is worth discussing an alternate strategy and the pros and cons.
Typically you would want to store a serialized version of your protocol buffer, indexed by some particular key (a unique identifier, perhaps). You could then build secondary indexes for other interesting fields that point to that unique identifier. The idea is that you would want explicit indexes like this to scale beyond what a system that provides arbitrary indexes. This obviously opens up a world of new problems (such as stale arbitrary indexes).
ClickHouse 最近添加了对 protobuf 消息的支持。
ClickHouse lately added support for protobuf messages.
这是我找到的一个项目: https://github.com/google/mysql-protobuf
这是使用 protobuf 的 sql,看起来很有前途,但最后一次提交是在 2016 年 3 月中旬。
Here is a project I found: https://github.com/google/mysql-protobuf
It's sql that speaks protobuf, looks promising but last commit was in mid March 2016.
Cloud Spanner 将为 protobuf 提供本机支持。
https://cloud.google.com/spanner/
Cloud Spanner would provide native support for protobufs.
https://cloud.google.com/spanner/