Flink Community, Use Cases

Apache Flink® User Survey 2016 Results, Part 2

twitterredditlinkedinmailtwitterredditlinkedinmail
Last week, we published the first of two blog posts recapping the results of the 2016 Apache Flink® user survey. In part 1, we shared a selection of graphs summarizing responses to the survey’s multiple choice questions. In part 2, we’ll look at responses to the survey’s open-ended questions:
  • What new features or functionality would you like to see in Flink?
  • Please briefly describe the application(s) your team is building or plans to build with Flink.
  • Are there any other challenges (when working with Flink) not listed (in the previous question) that you’d like to mention?
  • What other sources / sinks not included in the list (that was provided in the survey), if any, are important for your Flink application?
  • We welcome any final comments about any aspect of Flink.
Some background information: one of the questions in the survey asked respondents if it was okay to share anonymous and unattributed responses or quotes in the post-survey recap, and 67 of 119 respondents gave permission to share their responses. The answers in this post come from more than half, but not all, of the survey-takers. And we won’t be including any company or personal information in these responses–we removed information from open-ended responses that we thought might reveal who provided it. In this post, we’ll include a subset of open-ended responses that are indicative of patterns or common themes, and if you want to see all responses from respondents who gave their permission to share, we’ve created a GitHub repo that contains all survey-related materials. In some cases, we edited responses for readability but otherwise left them untouched, so what you’re seeing is raw feedback from Flink users.

1. What new features or functionality would you like to see in Flink?

2. Please briefly describe the application(s) your team is building or plans to build with Flink.
3. Are there any other challenges (with Flink) not listed above that you’d like to mention?
4. What other sources / sinks not included in the list above, if any, are important for your Flink application?
5. We welcome any final comments about any aspect of Flink.

What new features or functionality would you like to see in Flink?

See the complete list here.

Please briefly describe the application(s) your team is building or plans to build with Flink.

See the complete list here.

Are there any other challenges (with Flink) not listed above that you’d like to mention?

See the complete list here.

What other sources / sinks not included in the list above, if any, are important for your Flink application?

See the complete list here.

We welcome any final comments about any aspect of Flink.

See the complete list here. That concludes our review of the 2016 Apache Flink user survey. We hope that we were able to provide the Flink community with a broader view of Flink usage and to help identify potential areas for improvement in the coming months. The community welcomes new contributors, and if you’re interested, you can learn more here.
twitterredditlinkedinmailtwitterredditlinkedinmail