<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Rowfire blog</title><description>Database events, explained: turning what happens in PostgreSQL and MySQL into alerts, tickets, campaigns and API calls.</description><link>https://rowfire.com/</link><item><title>Sixteen workers, one send: deduplicating with a ledger</title><link>https://rowfire.com/blog/sixteen-workers-one-send/</link><guid isPermaLink="true">https://rowfire.com/blog/sixteen-workers-one-send/</guid><description>Why Rowfire sends only when an INSERT reports it inserted a row, and how that one rule keeps 16 racing workers from sending the same message 16 times.</description><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate></item><item><title>The events your app can&apos;t emit</title><link>https://rowfire.com/blog/the-events-your-app-cant-emit/</link><guid isPermaLink="true">https://rowfire.com/blog/the-events-your-app-cant-emit/</guid><description>Your application emits events when its code runs. It can&apos;t announce what didn&apos;t happen. Here is how a SQL trigger catches absences and derived conditions.</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>