<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api Monitoring on precomputing.com</title>
    <link>https://precomputing.com/tags/api-monitoring/</link>
    <description>Recent content in Api Monitoring on precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/api-monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Latency Case Study: A Million Requests Kept as Ready Answers Inside SQLite</title>
      <link>https://precomputing.com/api-latency-case-study-a-million-requests-kept-as-ready-answers-inside-sqlite/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/api-latency-case-study-a-million-requests-kept-as-ready-answers-inside-sqlite/</guid>
      <description>&lt;p&gt;A small web service that already keeps its data in SQLite wants the usual answers about its API: how many requests each endpoint gets, how long they take on average, and the p99. The simple way is a table with a row per request, scanned whenever someone looks. In the SQL demo the service keeps a compiled Precomputing policy in the same SQLite instead, and the answers stay current on every insert.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
