re: The Cloud Is the New OS - A Developer's Perspective VIEW POST

VIEW FULL DISCUSSION
 

The biggest and probably most wanted thing about cloud is that is provides standard implementations and finally defines infrastructure on a usable level.

OCCI as definition of that is of much more significance than AWS, GCE, etc. Why? Because it sheds a light into a field that was mostly filled with ad-hoc impromptu solutions.

Need a machine? Let me fire that up, execute random, never recorded commands, connect that router and be done.

Cloud infrastructure still has all that but in a structured way, everything is defined, documented, recorded. And thanks to OCCI we now get to replicate real world infrastructure as software/code which then can be used to construct virtual data centres.

Downsides? Control. You mention giving up control to move to the cloud, and I say: control is what can kill all cloud providers.

Compliance regulations impose the need for control. Or cloud providers will have to assume legal liability for these topics. Given how much cloud porviders love doing that, I think we will see a shift from using cloud infrastructure to more and more cloud providers delivering packaged solutions for running a cloud alike infrastructure on site.

 

TIL about OCCI - thanks Daniel :)

This looks to be heading in the right direction, along with commercial competition from the likes of Terraform, to providing a common cloud infrastructure API, with aspirations to move 'up the stack' and manage PaaS and SaaS, maybe FaaS deployment - good!

I'm also interested in the ongoing process of decoupling and standardizing the API used by that all important business logic: we've gone from libc + targeted binaries, via virtual machine APIs (JVM, CLR) and interpreted/JIT (Python, Ruby, ECMAscript), into containers (Docker, Solaris Containers, OpenVZ, BSD jail, ...), and Serverless/FaaS (AWS Lambda, Azure FaaS, Google Functions, Cloudflare Workers) where we can finally stop thinking about machines and OSes. Right now there are significant API differences across vendors (they need their lock in!) but I'm hoping this will resolve into a portable Serverless API. Early adopters can choose their vendor or use abstraction layers such as serverless.com/ although this provides a low common denominator ATM.

code of conduct - report abuse