Quick Start Guide: Reactive Tweets

Quick Start Guide: Reactive Tweets

A typical use case for stream processing is consuming a live stream of data that we want to extract or aggregate some other data from. In this example we'll consider consuming a stream of tweets and extracting information concerning Akka from them.

We will also consider the problem inherent to all non-blocking streaming solutions: "What if the subscriber is too slow to consume the live stream of data?". Traditionally the solution is often to buffer the elements, but this can—and usually will—cause eventual buffer overflows and instability of such systems. Instead Akka Streams depend on internal backpressure signals that allow to control what should happen in such scenarios.

Here's the data model we'll be working with throughout the quickstart examples:

public static class Author {
  public final String handle;

  public Author(String handle) {
    this.handle = handle;

  // ...


public static class Hashtag {
  public final String name;

  public Hashtag(String name) {
    this.name = name;

  // ...

public static class Tweet {
  public final Author author;
  public final long timestamp;
  public final String body;

  public Tweet(Author author, long timestamp, String body) {
    this.author = author;
    this.timestamp = timestamp;
    this.body = body;

  public Set<Hashtag> hashtags() {
    return Arrays.asList(body.split(" ")).stream()
      .filter(a -> a.startsWith("#"))
      .map(a -> new Hashtag(a))

  // ...

public static final Hashtag AKKA = new Hashtag("#akka");


If you would like to get an overview of the used vocabulary first instead of diving head-first into an actual example you can have a look at the Core concepts and Defining and running streams sections of the docs, and then come back to this quickstart to see it all pieced together into a simple example application.

Transforming and consuming simple streams

The example application we will be looking at is a simple Twitter feed stream from which we'll want to extract certain information, like for example finding all twitter handles of users who tweet about #akka.

In order to prepare our environment by creating an ActorSystem and ActorMaterializer, which will be responsible for materializing and running the streams we are about to create:

final ActorSystem system = ActorSystem.create("reactive-tweets");
final Materializer mat = ActorMaterializer.create(system);

The ActorMaterializer can optionally take ActorMaterializerSettings which can be used to define materialization properties, such as default buffer sizes (see also Buffers in Akka Streams), the dispatcher to be used by the pipeline etc. These can be overridden withAttributes on Flow, Source, Sink and Graph.

Let's assume we have a stream of tweets readily available, in Akka this is expressed as a Source:

Source<Tweet, BoxedUnit> tweets;

Streams always start flowing from a Source<Out,M1> then can continue through Flow<In,Out,M2> elements or more advanced graph elements to finally be consumed by a Sink<In,M3>.

The first type parameter—Tweet in this case—designates the kind of elements produced by the source while the M type parameters describe the object that is created during materialization (see below)—BoxedUnit (from the scala.runtime package) means that no value is produced, it is the generic equivalent of void.

The operations should look familiar to anyone who has used the Scala Collections library, however they operate on streams and not collections of data (which is a very important distinction, as some operations only make sense in streaming and vice versa):

final Source<Author, BoxedUnit> authors =
    .filter(t -> t.hashtags().contains(AKKA))
    .map(t -> t.author);

Finally in order to materialize and run the stream computation we need to attach the Flow to a Sink<T, M> that will get the flow running. The simplest way to do this is to call runWith(sink) on a Source<Out, M>. For convenience a number of common Sinks are predefined and collected as static methods on the Sink class. For now let's simply print each author:

authors.runWith(Sink.foreach(a -> System.out.println(a)), mat);

or by using the shorthand version (which are defined only for the most popular sinks such as Sink.fold and Sink.foreach):

authors.runForeach(a -> System.out.println(a), mat);

Materializing and running a stream always requires a Materializer to be passed in explicitly, like this: .run(mat).

The complete snippet looks like this:

final ActorSystem system = ActorSystem.create("reactive-tweets");
final Materializer mat = ActorMaterializer.create(system);

final Source<Author, BoxedUnit> authors =
    .filter(t -> t.hashtags().contains(AKKA))
    .map(t -> t.author);

authors.runWith(Sink.foreach(a -> System.out.println(a)), mat);

Flattening sequences in streams

In the previous section we were working on 1:1 relationships of elements which is the most common case, but sometimes we might want to map from one element to a number of elements and receive a "flattened" stream, similarly like flatMap works on Scala Collections. In order to get a flattened stream of hashtags from our stream of tweets we can use the mapConcat combinator:

final Source<Hashtag, BoxedUnit> hashtags =
  tweets.mapConcat(t -> new ArrayList<Hashtag>(t.hashtags()));


The name flatMap was consciously avoided due to its proximity with for-comprehensions and monadic composition. It is problematic for two reasons: firstly, flattening by concatenation is often undesirable in bounded stream processing due to the risk of deadlock (with merge being the preferred strategy), and secondly, the monad laws would not hold for our implementation of flatMap (due to the liveness issues).

Please note that the mapConcat requires the supplied function to return a strict collection (Out f -> java.util.List<T>), whereas flatMap would have to operate on streams all the way through.

Broadcasting a stream

Now let's say we want to persist all hashtags, as well as all author names from this one live stream. For example we'd like to write all author handles into one file, and all hashtags into another file on disk. This means we have to split the source stream into 2 streams which will handle the writing to these different files.

Elements that can be used to form such "fan-out" (or "fan-in") structures are referred to as "junctions" in Akka Streams. One of these that we'll be using in this example is called Broadcast, and it simply emits elements from its input port to all of its output ports.

Akka Streams intentionally separate the linear stream structures (Flows) from the non-linear, branching ones (Graphs) in order to offer the most convenient API for both of these cases. Graphs can express arbitrarily complex stream setups at the expense of not reading as familiarly as collection transformations.

Graphs are constructed using GraphDSL like this:

Sink<Author, BoxedUnit> writeAuthors;
Sink<Hashtag, BoxedUnit> writeHashtags;
RunnableGraph.fromGraph(GraphDSL.create(b -> {
  final UniformFanOutShape<Tweet, Tweet> bcast = b.add(Broadcast.create(2));
  final FlowShape<Tweet, Author> toAuthor =
	  b.add(Flow.of(Tweet.class).map(t -> t.author));
  final FlowShape<Tweet, Hashtag> toTags =
      b.add(Flow.of(Tweet.class).mapConcat(t -> new ArrayList<Hashtag>(t.hashtags())));
  final SinkShape<Author> authors = b.add(writeAuthors);
  final SinkShape<Hashtag> hashtags = b.add(writeHashtags);

  return ClosedShape.getInstance();

As you can see, we use graph builder b to construct the graph using UniformFanOutShape and Flow s.

GraphDSL.create returns a Graph, in this example a Graph<ClosedShape,Unit> where ClosedShape means that it is a fully connected graph or "closed" - there are no unconnected inputs or outputs. Since it is closed it is possible to transform the graph into a RunnableGraph using RunnableGraph.fromGraph. The runnable graph can then be run() to materialize a stream out of it.

Both Graph and RunnableGraph are immutable, thread-safe, and freely shareable.

A graph can also have one of several other shapes, with one or more unconnected ports. Having unconnected ports expresses a grapth that is a partial graph. Concepts around composing and nesting graphs in large structures are explained explained in detail in Modularity, Composition and Hierarchy. It is also possible to wrap complex computation graphs as Flows, Sinks or Sources, which will be explained in detail in Constructing and combining Partial Graphs.

Back-pressure in action

One of the main advantages of Akka Streams is that they always propagate back-pressure information from stream Sinks (Subscribers) to their Sources (Publishers). It is not an optional feature, and is enabled at all times. To learn more about the back-pressure protocol used by Akka Streams and all other Reactive Streams compatible implementations read Back-pressure explained.

A typical problem applications (not using Akka Streams) like this often face is that they are unable to process the incoming data fast enough, either temporarily or by design, and will start buffering incoming data until there's no more space to buffer, resulting in either OutOfMemoryError s or other severe degradations of service responsiveness. With Akka Streams buffering can and must be handled explicitly. For example, if we are only interested in the "most recent tweets, with a buffer of 10 elements" this can be expressed using the buffer element:

  .buffer(10, OverflowStrategy.dropHead())
  .map(t -> slowComputation(t))
  .runWith(Sink.ignore(), mat);

The buffer element takes an explicit and required OverflowStrategy, which defines how the buffer should react when it receives another element while it is full. Strategies provided include dropping the oldest element (dropHead), dropping the entire buffer, signalling failures etc. Be sure to pick and choose the strategy that fits your use case best.

Materialized values

So far we've been only processing data using Flows and consuming it into some kind of external Sink - be it by printing values or storing them in some external system. However sometimes we may be interested in some value that can be obtained from the materialized processing pipeline. For example, we want to know how many tweets we have processed. While this question is not as obvious to give an answer to in case of an infinite stream of tweets (one way to answer this question in a streaming setting would to create a stream of counts described as "up until now, we've processed N tweets"), but in general it is possible to deal with finite streams and come up with a nice result such as a total count of elements.

First, let's write such an element counter using Flow.of(Class) and Sink.fold to see how the types look like:

final Sink<Integer, Future<Integer>> sumSink =
  Sink.<Integer, Integer>fold(0, (acc, elem) -> acc + elem);

final RunnableGraph<Future<Integer>> counter =
    tweets.map(t -> 1).toMat(sumSink, Keep.right());

final Future<Integer> sum = counter.run(mat);

sum.foreach(new Foreach<Integer>() {
  public void each(Integer c) {
    System.out.println("Total tweets processed: " + c);
}, system.dispatcher());

First we prepare a reusable Flow that will change each incoming tweet into an integer of value 1. We combine all values of the transformed stream using Sink.fold will sum all Integer elements of the stream and make its result available as a Future<Integer>. Next we connect the tweets stream though a map step which converts each tweet into the number 1, finally we connect the flow using toMat the previously prepared Sink.

Remember those mysterious Mat type parameters on Source<Out, Mat>, Flow<In, Out, Mat> and Sink<In, Mat>? They represent the type of values these processing parts return when materialized. When you chain these together, you can explicitly combine their materialized values: in our example we used the Keep.right predefined function, which tells the implementation to only care about the materialized type of the stage currently appended to the right. As you can notice, the materialized type of sumSink is Future<Integer> and because of using Keep.right, the resulting RunnableGraph has also a type parameter of Future<Integer>.

This step does not yet materialize the processing pipeline, it merely prepares the description of the Flow, which is now connected to a Sink, and therefore can be run(), as indicated by its type: RunnableGraph<Future<Integer>>. Next we call run() which uses the ActorMaterializer to materialize and run the flow. The value returned by calling run() on a RunnableGraph<T> is of type T. In our case this type is Future<Integer> which, when completed, will contain the total length of our tweets stream. In case of the stream failing, this future would complete with a Failure.

A RunnableGraph may be reused and materialized multiple times, because it is just the "blueprint" of the stream. This means that if we materialize a stream, for example one that consumes a live stream of tweets within a minute, the materialized values for those two materializations will be different, as illustrated by this example:

final Sink<Integer, Future<Integer>> sumSink =
  Sink.<Integer, Integer>fold(0, (acc, elem) -> acc + elem);
final RunnableGraph<Future<Integer>> counterRunnableGraph =
    .filter(t -> t.hashtags().contains(AKKA))
    .map(t -> 1)
    .toMat(sumSink, Keep.right());

// materialize the stream once in the morning
final Future<Integer> morningTweetsCount = counterRunnableGraph.run(mat);
// and once in the evening, reusing the blueprint
final Future<Integer> eveningTweetsCount = counterRunnableGraph.run(mat);

Many elements in Akka Streams provide materialized values which can be used for obtaining either results of computation or steering these elements which will be discussed in detail in Stream Materialization. Summing up this section, now we know what happens behind the scenes when we run this one-liner, which is equivalent to the multi line version above:

final Future<Integer> sum = tweets.map(t -> 1).runWith(sumSink, mat);


runWith() is a convenience method that automatically ignores the materialized value of any other stages except those appended by the runWith() itself. In the above example it translates to using Keep.right as the combiner for materialized values.