<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on cloudplz</title><link>https://cloudplz.cc/tags/testing/</link><description>Recent content in Testing on cloudplz</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudplz.cc/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Database Canary Applications</title><link>https://cloudplz.cc/projects/database-canary-applications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://cloudplz.cc/projects/database-canary-applications/</guid><description>&lt;p&gt;When a platform team changes a Terraform module, bumps an engine version, or&#10;upgrades a connection library, the blast radius is every application built on&#10;top. Canary applications turn that blast radius into a tripwire.&lt;/p&gt;&#10;&lt;h2 id="challenge"&gt;Challenge&#10;&lt;/h2&gt;&#10;&lt;p&gt;Platform-level changes fail in ways unit tests don&amp;rsquo;t catch: a parameter group&#10;default that breaks connection pooling, a provider upgrade that drifts state,&#10;an engine version with different driver behavior. The first signal used to be&#10;a product team&amp;rsquo;s pager.&lt;/p&gt;</description></item></channel></rss>