<?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>Devops on Taubyte Blog</title><link>/blog/tags/devops/</link><description>Recent content in Devops 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>Fri, 27 Feb 2026 13:40:00 +0000</lastBuildDate><atom:link href="/blog/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Taubyte vs Traditional Cloud Workflows: What Teams Actually Care About</title><link>/blog/posts/taubyte-vs-traditional-cloud-workflows-what-teams-actually-care-about/</link><pubDate>Fri, 27 Feb 2026 13:40:00 +0000</pubDate><guid>/blog/posts/taubyte-vs-traditional-cloud-workflows-what-teams-actually-care-about/</guid><description>A practical comparison of Taubyte and traditional cloud workflows through the lens of speed, ownership, cost clarity, and long-term operational simplicity.</description></item><item><title>Microservices: What Amazon Prime Video Learned the Hard Way</title><link>/blog/posts/microservices-performance-fresser/</link><pubDate>Tue, 17 Feb 2026 16:00:00 +0000</pubDate><guid>/blog/posts/microservices-performance-fresser/</guid><description>Amazon Prime Video cut costs by 90% by moving away from microservices back to a monolith.</description></item><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><item><title>Kubernetes: The Orchestration Tax Most Teams Don't Need</title><link>/blog/posts/kubernetes-performance-fresser/</link><pubDate>Sun, 15 Feb 2026 16:00:00 +0000</pubDate><guid>/blog/posts/kubernetes-performance-fresser/</guid><description>&lt;p>Kubernetes was built to orchestrate Google&amp;rsquo;s global infrastructure. You are not Google. Terribly sorry.&lt;/p>
&lt;p>82% of container users run Kubernetes in production. Most of them shouldn&amp;rsquo;t.&lt;/p>
&lt;h2 id="the-control-plane-tax">The Control Plane Tax&lt;/h2>
&lt;p>Before your application serves a single request, Kubernetes needs etcd chewing through 2-8 GB RAM per node. Then kube-apiserver, kube-scheduler, kube-controller-manager, kubelet (reserving 25% of node memory by default), CoreDNS, kube-proxy, and a CNI plugin. All of this before your code runs.&lt;/p></description></item></channel></rss>