<?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>Paas on Brave New Geek</title><link>https://bravenewgeek.com/tag/paas/</link><description>Recent content in Paas on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Feb 2018 16:26:31 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/paas/index.xml" rel="self" type="application/rss+xml"/><item><title>There and Back Again: Why PaaS Is Passé (And Why It’s Not)</title><link>https://bravenewgeek.com/there-and-back-again-why-paas-is-passe-and-why-its-not/</link><pubDate>Tue, 06 Feb 2018 16:26:31 -0600</pubDate><guid>https://bravenewgeek.com/there-and-back-again-why-paas-is-passe-and-why-its-not/</guid><description>&lt;p&gt;In 10 years nobody will be talking about Kubernetes. Not because people stopped using it or because it fell out of favor, but because it became utility. Containers, Kubernetes, service meshes—they’ll all be there, the same way VMs, hypervisors, and switches will be. Compute is a commodity, and I don’t care how my workload runs so long as it meets my business’s SLOs and other requirements. Within AWS alone, there are now &lt;em&gt;innumerable&lt;/em&gt; ways to run a compute workload.&lt;/p&gt;</description></item></channel></rss>