<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Job-Scheduler on Lorbic</title>
    <link>https://lorbic.com/tags/job-scheduler/</link>
    <description>Recent content in Job-Scheduler on Lorbic</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 09 Aug 2026 14:00:00 +0530</lastBuildDate>
    <atom:link href="https://lorbic.com/tags/job-scheduler/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing a Distributed Job Scheduler in Go: Partitioning, Locking, and Backpressure</title>
      <link>https://lorbic.com/designing-a-distributed-job-scheduler/</link>
      <pubDate>Sun, 09 Aug 2026 14:00:00 +0530</pubDate>
      <guid>https://lorbic.com/designing-a-distributed-job-scheduler/</guid>
      <description>&lt;p&gt;Linux &lt;code&gt;crontab&lt;/code&gt; is one of the most elegant pieces of software ever written for single-host automation. It is simple, clear, and has kept Unix systems running reliably since 1975.&lt;/p&gt;&#xA;&lt;p&gt;The problem starts when we take a single-host tool and deploy it across a multi-node cloud setup.&lt;/p&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;https://lorbic.com/how-multi-tenant-saas-works/&#34;&gt;Relay&lt;/a&gt;, a multi-tenant AI API gateway system design, background jobs power core operations: every top of the hour, a job rolls up raw API usage tokens into tenant billing metrics; every 15 minutes, another job scans for expired API keys and purges them from cache; every 30 seconds, a health checker pings upstream LLM provider endpoints.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
