FlockDB
 | 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)
(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 is 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 is not designed for multi-hop graph traversal but rather for rapid set operations, not unlike the primary use-case for Redis sets.[4] Since it is still in the process of being packaged for outside of Twitter use, the code is still very rough and hence there is no stable release available yet. FlockDB was posted on GitHub shortly after Twitter released its Gizzard framework, which it uses to query the FlockDB distributed datastore. The database is licensed under the Apache License.[1]
See also[edit]
References[edit]
- ^ a b "FlockDB System Properties". db-engines.com. Retrieved 2017-10-09.
- ^ "FlockDB 1.8.5 released". Twitter. February 22, 2012. Retrieved 2 November 2013.
- ^ "Gigaom | Twitter Open-sources the Home of Its Social Graph". gigaom.com. Retrieved 16 September 2017.
- ^ "GitHub - twitter-archive/flockdb: A distributed, fault-tolerant graph database". github.com. Retrieved 16 September 2017.
