Skip to main content

Twitter's 100th open source GitHub repo - Summingbird


With the open sourcing of Twitter’s Summingbird library this week, we now have another ingenous option to integrate real-time and batch processing. Summingbird allows building MapReduce pipelines with simple primitives and merging data sets with low latency.

Working as an abstraction layer, it aims to separate the MapReduce computation and workflow from physical system layer. Within Twitter it has been used to deploy MapReduce workflow on Hadoop and Storm clusters. More specifically, the team of Oscar Boykin, Sam Ritchie and Ashutosh Singhal have been using this library to write MapReduce “streaming computation once and execute it in batch-mode on Scalding, in realtime mode on Storm, or on both Scalding and Storm in a hybrid batch/realtime mode.”

Summingbird’s real-time MapReduce DSL takes advantage of 3 computation libraries from Twitter:
•    Algebird: Abstract algebra library for Scala targeted at building aggregation systems
•    Bijection: An invertible function that converts back and forth between two types, with the contract that a round-trip through the Bijection will bring back the original object.
•    Storehaus: A library built on top of Twitter's Future that makes it easy to work with asynchronous key value stores.
The library leverages monoids in particular for advanced statistical analysis. Within Algebird, these find application for Bloom filters, HyperLogLog counters and count-min sketches. A monoid is a set that is closed under an associative binary operation and has an identity element I (element of) S such that for all a (element of) S, I a = a I = a.


Summingbird has been used to power Twitter headlines which shows stories related to tweets. It is also believed to be a key driver behind providing near real time views to advertisers on the Twitter advertisement dashboard. Another key milestone that the project would mark is that it shall be Twitter’s 100th public open source code repository on GitHub.

You may follow @summingbird for more updates. The source code has been released this week on https://github.com/twitter/summingbird.


------------------------------
update: 4 Sep 2013: text updated to reflect authors and link after the project release.

image source: Sam Ritchie/Twitter

Comments

Popular posts from this blog

In-memory data model with Apache Gora

Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice. This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora Although there are var…

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Amazon DynamoDB datastore for Gora

What was initially suggested during causal conversation at ApacheCon2011 in November 2011 as a “neat idea”, would soon become prime ground for Gora's first taste of participation within Google's Summer of Code program. Initially, the project, titled Amazon DynamoDB datastore for Gora, merely aimed to extend the Gora framework to Amazon DynamoDB. However, it seem became obvious that the issue would include much more than that simple vision.

The Gora 0.3 Toolbox We briefly digress to discuss some other noticeable additions to Gora in 0.3, namely: Modification of the Query interface: The Query interface was amended from Query<K, T> to Query<K, T extends Persistent> to be more precise and explicit for developers. Consequently all implementors and users of the Query interface can only pass object's of Persistent type. Logging improvements for data store mappings: A key aspect of using Gora well is the establishment and accurate definitio…