FlockDB——这是什么？以及它的最佳用途
刚刚接触到 FlockDB 图数据库。详细信息请参见 github /flockDB。 Twitter 声称它使用 FlockDB 来实现以下目的：
Twitter 在大型机器集群上运行 FlockDB。 我们用它来存储社交图谱（谁 跟随谁，谁阻止谁）和 Twitter 的二级索引。
乍一看，设置和尝试看起来并不简单。有人已经使用过/设置过它吗？如果是这样，请回答以下一般性问题。
- 它是什么样的应用程序 更适合？ （推特声称 很简单，很粗糙，但仍然 看看它的意思）
- FlockDB 比其他图形数据库更好/ noSQL 数据库。你设置FlockDB了吗？ 将其用于应用程序？
- 早期的建议有吗？
注意：我评估 FlockDB 和其他图数据库主要是为了学习它们。也许，我会为此构建一个应用程序。
Just came across FlockDB graph database. Details at github /flockDB. Twitter claims it uses FlockDB for the following:
Twitter runs FlockDB on a large cluster of machines.
we use it to store social graphs (who
follows whom, who blocks whom) and
secondary indices at twitter.
At first glance, setup and trying it doesn't look straight forward. Have anyone already used it / setup this? If so, please answer the following general queries.
- What kind of applications is it
better suited for? (Twitter claims it
is simple and very rough, it remains
to see what it meant though) - How is FlockDB better than other graph db /
noSQL db. Have you setup FlockDB,
used it for a application? - Early advices any?
Note: I am evaluating the FlockDB and other graph databases mainly for learning them. Perhaps, I will build an application for that.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Flockdb 尚未由 Twitter 发布，这意味着您看到的当前版本将无法正常运行。根据提交的历史记录，我想在几天之内您就可以看到一个可以构建和测试的稳定版本。
与 Neo4J 之类的数据库相比，您可以说 Flockdb 甚至不是图形数据库。图数据库最困难的部分是它可以处理多少个深度级别。从 Flockdb 的小文档来看，它似乎无法处理超过 1 级的深度。与 Neo4J 等数据库相比，FlockDb 的优势在于它的低延迟、高吞吐量和固有的分布式特性。
关于应用程序 - 我想每当您需要社交网络或 Twitter 之类的行为时，它都会非常适合。不过，我认为没有多少人会发现这样的用例（谁每秒会收到 20k 个好友请求？）。
我刚刚开始研究 Flockdb。现在我计划在我的论坛软件中使用它。我计划将其用于 user1 阅读 post1、user1 收藏 post1 等，而不是 user1 遵循 user2 关系。作为高度活跃的在线社区之一，我们获得了大量此类流量（阅读/收藏）。现在想不出任何其他用例。
Flockdb is still Yet to be released by Twitter, which means the current version you are seeing won't run properly. Going by the history of commits i guess within a couple of days you can see a stable version which you can build and test.
Compared to something like Neo4J you can say Flockdb is not even a graph database. The toughest part of a graph database is how many levels of depth it can handle. From the little documentation of Flockdb it seems like it can't handle more than 1 level of depth. Where FlockDb wins compared to DBs like Neo4J is it's low latency, high throughput and inherent distributed nature.
Regarding Applications - i guess it will be a great fit whenever you need social networking or twitter like behavior. I don't think many will find such use cases though (who gets 20k friend requests per sec ?).
I Just started looking into Flockdb. Right now i am planning to use it in my forum software. Instead of user1 follows user2 relationship, i am planning to use it for user1 read post1, user1 favorites post1 etc. Being one of the highly active online communities we get a lot of such traffic(read/favorite). Can't think of any other use cases now.
不要错过OrientDB。它是一个文档图数据库管理系统，具有用于遍历关系的特殊运算符：http://code.google .com/p/orient/wiki/GraphDatabase
Don't miss OrientDB. It's a document-graph dbms with special operator for traversing relationships: http://code.google.com/p/orient/wiki/GraphDatabase