<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Orchestration on Danilo Falcão da Silva</title><link>https://falcao.org/tags/orchestration/</link><description>Recent content in Orchestration on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Jun 2026 13:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/orchestration/index.xml" rel="self" type="application/rss+xml"/><item><title>Nomad: What If You Don't Need Kubernetes?</title><link>https://falcao.org/posts/nomad-what-if-you-dont-need-kubernetes/</link><pubDate>Fri, 19 Jun 2026 13:00:00 -0300</pubDate><guid>https://falcao.org/posts/nomad-what-if-you-dont-need-kubernetes/</guid><description>&lt;p>There&amp;rsquo;s a reflex in this industry that nobody questions anymore.
You have a few services to run. Maybe a handful of containers, a
couple of background workers, a cron job or two. And the very first
architecture decision — before anyone has asked what the workload
actually needs — is &lt;em>&amp;ldquo;so which Kubernetes are we using?&amp;rdquo;&lt;/em>&lt;/p>
&lt;p>Kubernetes is the default answer to a question most teams never
bothered to ask. &lt;strong>Nomad is the question.&lt;/strong> Specifically: do you
actually need all of that?&lt;/p></description></item></channel></rss>