This is the second blog post in our series on how Flink enables new streaming applications. The first post introduced event time and out of order processing. This post is about versioning application state, and will be followed by a post about sessions and advanced windows.
Until very recently I’ve been working at Twitter and focusing primarily on stream processing systems. While researching the current state-of-the-art in stateful streaming systems I came across Apache Flink™. I’ve known for some time that having proper, fault-tolerant, managed state and exactly-once processing semantics with regard to that state was going to be a game changer for stream processing so when I came across Apache Flink™ I was understandably excited.