<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Etl on Project Wintermute</title><link>https://wintermutecore.com/tags/etl/</link><description>Recent content in Etl on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 18 Mar 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://wintermutecore.com/tags/etl/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a daily data pipeline with Dagu, Python, and a JSONL data lake</title><link>https://wintermutecore.com/posts/daily-data-pipeline-dagu-python/</link><pubDate>Wed, 18 Mar 2026 08:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/daily-data-pipeline-dagu-python/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Three stages (ingest, index, alert), one stage per script, JSONL as the index format, a flat dedup state file, Dagu for scheduling. Boring, reliable, and dramatically less work than reaching for a heavyweight orchestrator.&lt;/p&gt;
&lt;p&gt;There is a class of pipeline that does not deserve a Spark cluster, an Airflow deployment, or a multi-tenant orchestrator. It is the &amp;ldquo;fetch a few hundred records from an API every day, index them, alert on the interesting ones&amp;rdquo; job. We have built this kind of thing dozens of times. Here is the shape that has held up.&lt;/p&gt;</description></item><item><title>Services</title><link>https://wintermutecore.com/services/</link><pubDate>Sun, 13 Feb 2022 11:11:11 -0100</pubDate><guid>https://wintermutecore.com/services/</guid><description>&lt;p&gt;&lt;p style="text-align:center;"&gt;
 &lt;img src="https://wintermutecore.com/services.jpg" alt="Services" /&gt;
&lt;/p&gt;
&lt;/p&gt;
&lt;p&gt;Below is what we actually do day to day. We try to keep the list short and the descriptions honest. If something here matches what you need, get in touch.&lt;/p&gt;

&lt;h2 id="software-engineering" class="anchor-link"&gt;&lt;a href="#software-engineering"&gt;Software engineering&lt;span class="pilcrow"&gt;&amp;nbsp;¶&lt;/span&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;We write backend services in Java, Kotlin, Go, and Groovy. Most of the work falls into a few buckets: REST and gRPC APIs, distributed systems handling high request volumes, and the occasional batch job that has to be reliable more than fast.&lt;/p&gt;</description></item></channel></rss>