<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hadoop on cloudmato.com</title><link>https://cloudmato.com/tags/hadoop/</link><description>Recent content in Hadoop on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Sun, 14 Jun 2026 21:29:11 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/hadoop/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Hadoop, and Why It Isn't 10 Microservices on K8s</title><link>https://cloudmato.com/posts/what-is-hadoop-vs-microservices-kubernetes/</link><pubDate>Sun, 14 Jun 2026 21:29:11 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/what-is-hadoop-vs-microservices-kubernetes/</guid><description>&lt;p&gt;Someone asked me this exact question last week, and it&amp;rsquo;s a good one because both setups &lt;em&gt;look&lt;/em&gt; the same if you squint. A bunch of machines, some shared storage in the middle, work spread across nodes. So why does one get called &amp;ldquo;big data&amp;rdquo; and the other &amp;ldquo;microservices&amp;rdquo;? Are they just two words for the same cluster? Honestly, no. They&amp;rsquo;re built on opposite assumptions about one thing: &lt;strong&gt;where the data lives and who moves to whom.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>