<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Apache Flink on Steffen Hausmann</title>
    <link>https://steffen.hausmann.info/tags/apache-flink/</link>
    <description>Recent content in Apache Flink on Steffen Hausmann</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 23 Nov 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://steffen.hausmann.info/tags/apache-flink/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Making it Easier to Build Connectors with Apache Flink: Introducing the Async Sink</title>
      <link>https://steffen.hausmann.info/posts/making-it-easier-to-build-connectors-with-apache-flink-introducing-the-async-sink/</link>
      <pubDate>Wed, 23 Nov 2022 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/making-it-easier-to-build-connectors-with-apache-flink-introducing-the-async-sink/</guid>
      <description>&lt;p&gt;Apache Flink is a popular open source framework for stateful computations over data streams. It allows you to formulate queries that are continuously evaluated in near real time against an incoming stream of events. To persist derived insights from these queries in downstream systems, Apache Flink comes with a rich connector ecosystem that supports a wide range of sources and destinations. However, the existing connectors may not always be enough to support all conceivable use cases. Our customers and the community kept asking for more connectors and better integrations with various open source tools and services.&lt;/p&gt;</description>
    </item>
    <item>
      <title>One Sink to Rule Them All: Introducing the New Async Sink</title>
      <link>https://steffen.hausmann.info/posts/one-sink-to-rule-them-all-introducing-the-new-async-sink/</link>
      <pubDate>Wed, 03 Aug 2022 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/one-sink-to-rule-them-all-introducing-the-new-async-sink/</guid>
      <description>&lt;p&gt;Next time you want to integrate with a new destination for a demo, concept or production application, the Async Sink framework will bootstrap development, allowing you to move quickly without compromise. In Flink 1.15 we introduced the Async Sink base (FLIP-171), with the goal to encapsulate common logic and allow developers to focus on the key integration code. The new framework handles things like request batching, buffering records, applying backpressure, retry strategies, and at least once semantics. It allows you to focus on your business logic, rather than spending time integrating with your downstream consumers. During the session we will dive deep into the internals to uncover how it works, why it was designed this way, and how to use it. We will code up a new sink from scratch and demonstrate how to quickly push data to a destination. At the end of this talk you will be ready to start implementing your own Flink sink using the new Async Sink framework.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flink Improvement Proposal 171: Async Sink </title>
      <link>https://steffen.hausmann.info/posts/flink-improvement-proposal-171-async-sink/</link>
      <pubDate>Wed, 09 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/flink-improvement-proposal-171-async-sink/</guid>
      <description>&lt;p&gt;Apache Flink has a rich connector ecosystem that can persist data in various destinations. Flink natively supports Apache Kafka, Amazon Kinesis Data Streams, Elasticsearch, HBase, and many more destinations. Additional connectors are maintained in Apache Bahir or directly on GitHub. The basic functionality of these sinks is quite similar. They batch events according to user defined buffering hints, sign requests and send them to the respective endpoint, retry unsuccessful or throttled requests, and participate in checkpointing. They primarily just differ in the way they interface with the destination. Yet, all the above-mentioned sinks are developed and maintained independently.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building real-time applications using Apache Flink</title>
      <link>https://steffen.hausmann.info/posts/building-real-time-applications-using-apache-flink/</link>
      <pubDate>Thu, 10 Dec 2020 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/building-real-time-applications-using-apache-flink/</guid>
      <description>&lt;p&gt;Build real-time applications using Apache Flink with Apache Kafka and Amazon Kinesis Data Streams. Apache Flink is a framework and engine for building streaming applications for use cases such as real-time analytics and complex event processing. This session covers best practices for building low-latency applications with Apache Flink when reading data from either Amazon MSK or Amazon Kinesis Data Streams. It also covers best practices for running low-latency Apache Flink applications using Amazon Kinesis Data Analytics and discusses AWS’s open-source contributions to this use case.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Streaming ETL with Apache Flink and Amazon Kinesis Data Analytics</title>
      <link>https://steffen.hausmann.info/posts/streaming-etl-with-apache-flink-and-amazon-kinesis-data-analytics/</link>
      <pubDate>Fri, 21 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/streaming-etl-with-apache-flink-and-amazon-kinesis-data-analytics/</guid>
      <description>&lt;p&gt;This post looks at how to use Apache Flink as a basis for sophisticated streaming extract-transform-load (ETL) pipelines. Apache Flink is a framework and distributed processing engine for processing data streams. AWS provides a fully managed service for Apache Flink through Amazon Kinesis Data Analytics, which enables you to build and run sophisticated streaming applications quickly, easily, and with low operational overhead.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://aws.amazon.com/blogs/big-data/streaming-etl-with-apache-flink-and-amazon-kinesis-data-analytics/&#34;&gt;https://aws.amazon.com/blogs/big-data/streaming-etl-with-apache-flink-and-amazon-kinesis-data-analytics/&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build real-time analytics for a ride-sharing app (ANT401)</title>
      <link>https://steffen.hausmann.info/posts/build-real-time-analytics-for-a-ride-sharing-app-ant401/</link>
      <pubDate>Mon, 02 Dec 2019 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/build-real-time-analytics-for-a-ride-sharing-app-ant401/</guid>
      <description>&lt;p&gt;In this session, we walk through how to perform real-time analytics on ride-sharing and taxi data, and we explore how to build a reliable, scalable, and highly available streaming architecture based on managed services. You learn how to deploy, operate, and scale an Apache Flink application with Amazon Kinesis Data Analytics for Java applications. Leave this workshop knowing how to build an end-to-end streaming analytics pipeline, starting with ingesting data into a Kinesis data stream, writing and deploying a Flink application to perform basic stream transformations and aggregations, and persisting the results to Amazon Elasticsearch Service to be visualized from Kibana.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics (FF)</title>
      <link>https://steffen.hausmann.info/posts/build-and-run-streaming-applications-with-apache-flink-and-amazon-kinesis-data-analytics-ff/</link>
      <pubDate>Tue, 08 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/build-and-run-streaming-applications-with-apache-flink-and-amazon-kinesis-data-analytics-ff/</guid>
      <description>&lt;p&gt;Stream processing facilitates the collection, processing, and analysis of real-time data and enables the continuous generation of insights and quick reactions to emerging situations. Yet, despite these advantages compared to traditional batch-oriented analytics applications, streaming applications are much more challenging to operate. Some of these challenges include the ability to provide and maintain low end-to-end latency, to seamlessly recover from failure, and to deal with a varying amount of throughput.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Streaming Analytics Workshop</title>
      <link>https://steffen.hausmann.info/posts/streaming-analytics-workshop/</link>
      <pubDate>Thu, 20 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/streaming-analytics-workshop/</guid>
      <description>&lt;p&gt;In this workshop, you will build an end-to-end streaming architecture to ingest, analyze, and visualize streaming data in near real-time. You set out to improve the operations of a taxi company in New York City. You’ll analyze the telemetry data of a taxi fleet in New York City in near-real time to optimize their fleet operations.&lt;/p&gt;
&lt;p&gt;You will not only learn how to deploy, operate, and scale an Apache Flink application with Kinesis Data Analytics for Java Applications, but also explore the basic concepts of Apache Flink and running Flink applications in a fully managed environment on AWS.v&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics</title>
      <link>https://steffen.hausmann.info/posts/build-and-run-streaming-applications-with-apache-flink-and-amazon-kinesis-data-analytics/</link>
      <pubDate>Tue, 16 Apr 2019 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/build-and-run-streaming-applications-with-apache-flink-and-amazon-kinesis-data-analytics/</guid>
      <description>&lt;p&gt;Stream processing facilitates the collection, processing, and analysis of real-time data and enables the continuous generation of insights and quick reactions to emerging situations. This capability is useful when the value of derived insights diminishes over time. Hence, the faster you can react to a detected situation, the more valuable the reaction is going to be. Consider, for instance, a streaming application that analyzes and blocks fraudulent credit card transactions while they occur. Compare that application to a traditional batch-oriented approach that identifies fraudulent transactions at the end of every business day and generates a nice report for you to read the next morning.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Amazon Kinesis Analytics Taxi Consumer</title>
      <link>https://steffen.hausmann.info/posts/amazon-kinesis-analytics-taxi-consumer/</link>
      <pubDate>Fri, 15 Mar 2019 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/amazon-kinesis-analytics-taxi-consumer/</guid>
      <description>&lt;p&gt;Sample Apache Flink application that can be deployed to Kinesis Analytics for Java. It reads taxi events from a Kinesis data stream, processes and aggregates them, and ingests the result to an Amazon Elasticsearch Service cluster for visualization with Kibana.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/aws-samples/amazon-kinesis-analytics-taxi-consumer&#34;&gt;https://github.com/aws-samples/amazon-kinesis-analytics-taxi-consumer&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build a Real-time Stream Processing Pipeline with Apache Flink on AWS (FF)</title>
      <link>https://steffen.hausmann.info/posts/build-a-real-time-stream-processing-pipeline-with-apache-flink-on-aws-ff/</link>
      <pubDate>Wed, 13 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/build-a-real-time-stream-processing-pipeline-with-apache-flink-on-aws-ff/</guid>
      <description>&lt;p&gt;The increasing number of available data sources in today&amp;rsquo;s application stacks created a demand to continuously capture and process data from various sources to quickly turn high volume streams of raw data into actionable insights. Apache Flink addresses many of the challenges faced in this domain as it&amp;rsquo;s specifically tailored to distributed computations over streams. While Flink provides all the necessary capabilities to process streaming data, provisioning and maintaining a Flink cluster still requires considerable effort and expertise. We will discuss how cloud services can remove most of the burden of running the clusters underlying your Flink jobs and explain how to build a real-time processing pipeline on top of AWS by integrating Flink with Amazon Kinesis and Amazon EMR. We will furthermore illustrate how to leverage the reliable, scalable, and elastic nature of the AWS cloud to effectively create and operate your real-time processing pipeline with little operational overhead.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build a Real-time Stream Processing Pipeline with Apache Flink on AWS</title>
      <link>https://steffen.hausmann.info/posts/build-a-real-time-stream-processing-pipeline-with-apache-flink-on-aws/</link>
      <pubDate>Fri, 21 Apr 2017 00:00:00 +0000</pubDate>
      <guid>https://steffen.hausmann.info/posts/build-a-real-time-stream-processing-pipeline-with-apache-flink-on-aws/</guid>
      <description>&lt;p&gt;In today’s business environments, data is generated in a continuous fashion by a steadily increasing number of diverse data sources. Therefore, the ability to continuously capture, store, and process this data to quickly turn high-volume streams of raw data into actionable insights has become a substantial competitive advantage for organizations.&lt;/p&gt;
&lt;p&gt;Apache Flink is an open source project that is well-suited to form the basis of such a stream processing pipeline. It offers unique capabilities that are tailored to the continuous analysis of streaming data. However, building and maintaining a pipeline based on Flink often requires considerable expertise, in addition to physical resources and operational efforts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
