FlockDB

Today, FlockDB is a topic of great relevance and interest. Since its emergence, it has captured the attention of many people and has become a point of discussion in various areas. This phenomenon has sparked the interest of experts and enthusiasts alike, generating extensive debate about its implications and consequences. FlockDB has proven to have a significant impact on modern society, and its influence is becoming increasingly evident in different aspects of daily life. In this article, we will thoroughly explore FlockDB and its relevance in the current context, analyzing its evolution, challenges and possible future scenarios.

Graph-based distributed data manager, project no longer maintained since 2012

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)

FlockDB

Original author(s)	Nick Kallen, Robey Pointer, John Kalucki and Ed Ceaser from Twitter
Developer(s)	Twitter
Initial release	April 2010 (April 2010)
Final release	1.8.5 / 23 February 2012; 12 years ago (2012-02-23)
Repository	github.com/twitter/flockdb
Written in	Scala, Java, Ruby
Type	Graph Database
License	Apache License 2.0
Website	github.com/twitter/flockdb

FlockDB was an open-source distributed, fault-tolerant graph database for managing wide but shallow network graphs. 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. 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.

Twitter no longer supports FlockDB.

See also

• Gizzard (Scala framework)

References

1. ^ ^{a b} "FlockDB System Properties". db-engines.com. Retrieved 2017-10-09.
2. ^ "FlockDB 1.8.5 released". Twitter. February 22, 2012. Retrieved 2 November 2013.
3. ^ "Gigaom | Twitter Open-sources the Home of Its Social Graph". gigaom.com. Archived from the original on 17 September 2017. Retrieved 16 September 2017.
4. ^ "GitHub - twitter-archive/flockdb: A distributed, fault-tolerant graph database". github.com. Retrieved 16 September 2017.
5. ^ "GitHub - twitter-archive/flockdb: A distributed, fault-tolerant graph database". github.com. Retrieved 27 May 2020. Twitter is no longer maintaining this project or responding to issues or PRs.

External links

• Official website