<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CDN on NasimLab</title><link>https://blog.nasimlab.com/tags/cdn/</link><description>Recent content in CDN on NasimLab</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 30 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.nasimlab.com/tags/cdn/index.xml" rel="self" type="application/rss+xml"/><item><title>TrailForge: Building a Storefront I Could Cache, Attack, and Measure</title><link>https://blog.nasimlab.com/posts/002-trailforge-cache-attack-measure/</link><pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.nasimlab.com/posts/002-trailforge-cache-attack-measure/</guid><description>&lt;h1 id="trailforge-building-a-storefront-i-could-cache-attack-and-measure"&gt;TrailForge: Building a Storefront I Could Cache, Attack, and Measure&lt;/h1&gt;&#10;&lt;p&gt;Most demo websites are built to be looked at. I built TrailForge to be tested.&lt;/p&gt;&#10;&lt;p&gt;TrailForge Commerce is a fictional outdoor-equipment store I originally created for a Cloudflare App Services customer roleplay. The scenario was familiar: a growing e-commerce company cared about performance because performance affected revenue, but it was also dealing with application-layer attacks, automated abuse, fraudulent logins, and checkout abuse. I did not want to walk into that conversation with only slides and a dashboard tour of an idle website. I wanted a real site, running on a real origin server, that I could cache, attack, watch, and measure while I explained what was happening.&lt;/p&gt;</description></item></channel></rss>