Why Cloud Still Feels Harder Than It Should Be

Cloud was supposed to make everything easier. In some ways, it absolutely has. You can spin up infrastructure in minutes, scale on demand, and deploy globally without ever touching a piece of hardware. That’s a massive shift from the days when a “deployment” meant racking servers and hoping you sized things correctly six months in advance. But if you’ve actually been in the trenches—even recently—you know the reality is a little messier. That’s where this episode of the TechSpective Podcast starts. I sat down with Harshit Omar, co-founder and CTO of FluidCloud, and we ended up digging into something that doesn’t get talked about enough: the gap between what cloud is supposed to be and what it actually looks like day to day. Because “the cloud” isn’t really a thing anymore. It’s a collection of platforms that all do roughly the same things… just differently enough to make your life harder. AWS, Azure, Google Cloud—they all check the same boxes at a high level. Compute, storage, networking, databases. But once you get past that surface layer, the differences start to matter. The way services are structured, the way they’re configured, the way they behave—it’s not interchangeable. Not even close. And that becomes a problem the moment you try to do anything beyond a single-cloud deployment. Multi-cloud sounds great in theory. Flexibility. Resilience. Avoiding vendor lock-in. All good things. But in practice, it usually means you’re juggling multiple sets of tools, multiple skill sets, and multiple ways of solving the same problem. Most teams don’t have deep expertise across multiple clouds. They might be strong in one. Maybe decent in a second. Beyond that, it gets thin fast. And even if you do have the talent, you’re still dealing with the reality that everything moves—constantly. New services, updated APIs, shifting best practices. What you knew a year ago doesn’t always map cleanly to what you’re doing today. We also got into something I’ve seen play out over and over again—the tension between speed and control. Developers want to move fast. That’s their job. The cloud makes it easy to spin things up, try things out, and iterate quickly. But someone still has to manage cost, enforce security, and keep everything from turning into chaos. That responsibility doesn’t go away just because the infrastructure is abstracted. The old world had its limitations, but it was predictable. You knew what you had because you could point to it. Now, your environment can change in real time, and not always in ways you expect. That’s powerful, but it’s also a little dangerous if you don’t have the right visibility and controls in place. One of the more interesting parts of the conversation was looking ahead a bit—not in some five-year crystal ball way, but just where things seem to be heading. Right now, cloud providers still benefit from a certain amount of friction. Once you’re in, you’re kind of in. Moving workloads somewhere else is possible, but it’s not trivial. That friction keeps customers sticky. But what happens if that changes? What happens if moving between clouds becomes easy enough that it’s just… a choice? That’s not a small shift. If organizations can move workloads without a ton of overhead, it forces cloud providers to compete differently. It’s no longer about who you’re locked into. It’s about who actually delivers the best experience, performance, and cost. We’re not fully there yet, but you can see the direction things are going. This episode doesn’t try to wrap that up with a neat conclusion, because there isn’t one. It’s a real conversation about what’s working, what isn’t, and where things might be headed next. If you spend any time dealing with cloud, DevOps, or security, this will probably sound familiar.