Software:FlockDB
From HandWiki
Short description: Graph-based distributed data manager, project no longer maintained since 2012
| 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] |
| 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]
See also
References
- ↑ 1.0 1.1 "FlockDB System Properties" (in en). https://db-engines.com/en/system/FlockDB.
- ↑ "FlockDB 1.8.5 released". Twitter. February 22, 2012. https://github.com/twitter/flockdb/releases.
- ↑ "Gigaom | Twitter Open-sources the Home of Its Social Graph". http://gigaom.com/2010/04/12/twitter-open-sources-the-home-of-its-social-graph/.
- ↑ "GitHub - twitter-archive/flockdb: A distributed, fault-tolerant graph database". https://github.com/twitter/flockdb#readme.
- ↑ "GitHub - twitter-archive/flockdb: A distributed, fault-tolerant graph database". https://github.com/twitter-archive/flockdb. "Twitter is no longer maintaining this project or responding to issues or PRs."
External links
 |  |
