<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Next.js on David Cajio | AWS, DevOps &amp; Platform Reliability</title><link>https://davidcajio.com/tags/next.js/</link><description>Recent content in Next.js on David Cajio | AWS, DevOps &amp; Platform Reliability</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 David Cajio</copyright><lastBuildDate>Thu, 30 Jul 2026 18:50:00 -0400</lastBuildDate><atom:link href="https://davidcajio.com/tags/next.js/index.xml" rel="self" type="application/rss+xml"/><item><title>When Bot Traffic Becomes an Infrastructure Problem</title><link>https://davidcajio.com/posts/bot-traffic-infrastructure-cost-autoscaling/</link><pubDate>Thu, 30 Jul 2026 18:50:00 -0400</pubDate><guid>https://davidcajio.com/posts/bot-traffic-infrastructure-cost-autoscaling/</guid><description>&lt;p&gt;Bot traffic used to be background noise for us.&lt;/p&gt;
&lt;p&gt;It accounted for perhaps 10% to 15% of our requests. It was something we monitored, occasionally adjusted a firewall rule around, and otherwise treated as a normal part of operating a public e-commerce platform.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/bot-traffic-infrastructure-cost-autoscaling/feature.jpg"/></item></channel></rss>