<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nginx on Taubyte Blog</title><link>/blog/tags/nginx/</link><description>Recent content in Nginx on Taubyte Blog</description><image><title>Taubyte Blog</title><url>/blog/opengraph.jpg</url><link>/blog/opengraph.jpg</link></image><generator>Hugo -- 0.146.0</generator><language>en-us</language><lastBuildDate>Mon, 16 Feb 2026 16:00:00 +0000</lastBuildDate><atom:link href="/blog/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>NGINX: When Reverse Proxies Cost More Than They're Worth</title><link>/blog/posts/nginx-performance-fresser/</link><pubDate>Mon, 16 Feb 2026 16:00:00 +0000</pubDate><guid>/blog/posts/nginx-performance-fresser/</guid><description>&lt;p>NGINX sits between your users and your application. Before a single request reaches your code, NGINX is parsing configs, terminating SSL, rewriting URLs, and logging everything. All of this overhead. All of this complexity.&lt;/p>
&lt;p>The Ingress-NGINX controller is being retired in March 2026. About 50% of cloud-native setups depend on it. No more fixes. No more patches. Migrating means rewriting ingress configs across hundreds of services. Staying means increasing security risk. Pick your poison.&lt;/p></description></item></channel></rss>