This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "FlockDB" – news · newspapers · books · scholar · JSTOR (March 2013) (Learn how and when to remove this template message)
The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.Find sources: "FlockDB" – news · newspapers · books · scholar · JSTOR (March 2013) (Learn how and when to remove this template message)
(Learn how and when to remove this template message)
| Original author(s) | Nick Kallen, Robey Pointer, John Kalucki and Ed Ceaser from Twitter |
|---|---|
| Developer(s) | Twitter[1] |
| Initial release | April 2010 |
| Final release | 1.8.5
/ 23 February 2012[2] |
| Repository | |
| Written in | Scala, Java, Ruby |
| Type | Graph Database |
| License | Apache License 2.0 |
| Website | github |
FlockDB was an open-source distributed, fault-tolerant graph database for managing wide but shallow network graphs.[3] It was initially used by Twitter to store relationships between users, e.g. followings and favorites. FlockDB differs from other graph databases, e.g. Neo4j in that it was not designed for multi-hop graph traversal but rather for rapid set operations, not unlike the primary use-case for Redis sets.[4] FlockDB was posted on GitHub shortly after Twitter released its Gizzard framework, which it used to query the FlockDB distributed datastore. The database is licensed under the Apache License.[1]
Twitter no longer supports FlockDB.[5]
