<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flink on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/flink/</link><description>Recent content in Flink on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 02 May 2025 07:00:03 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/flink/index.xml" rel="self" type="application/rss+xml"/><item><title>A Tale of Two Runtimes: Setting Up Your Local Java Development with Flink</title><link>https://javapro-en.svenruppert.com/a-tale-of-two-runtimes-setting-up-your-local-java-development-with-flink/</link><pubDate>Fri, 02 May 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/a-tale-of-two-runtimes-setting-up-your-local-java-development-with-flink/</guid><description>&lt;p&gt;It was the best of builds, it was the worst of builds. One ran effortlessly in the IDE, the other stubbornly broke at runtime. Welcome to the tale of two runtimes: your local development setup and the Flink cluster where your job is ultimately meant to live.&lt;/p&gt;
&lt;p&gt;In this post, we’ll walk through how to set up your Flink Java project so you can develop, test, and run it locally with ease. Just like Charles Dickens’s works, if you’re just getting started with Apache Flink, the setup can feel a bit intimidating&amp;hellip;&lt;/p&gt;</description></item></channel></rss>