<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>serverless on The Joko Engineering Blog</title>
    <link>/tags/serverless/</link>
    <description>Recent content in serverless on The Joko Engineering Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/serverless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Fragile Pipelines to Durable Workflows</title>
      <link>/posts/from-fragile-pipelines-to-durable-workflows/</link>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/from-fragile-pipelines-to-durable-workflows/</guid>
      <description>At Joko, we&amp;rsquo;re building Juno: an AI shopping agent that helps people find the right product at the right price across thousands of merchants. To do that well, Juno needs a fresh, accurate, and complete view of what&amp;rsquo;s for sale on the internet: which means continuously ingesting and standardizing a very large product catalog (we&amp;rsquo;re talking about hundreds of millions of products).
That catalog is where this story starts.
1. Workflows look simple!</description>
    </item>
    
  </channel>
</rss>
