The M in MVC (Minimum Viable Cloud) implies that there are additional capabilities in a mature cloud implementation beyond those outlined in our previous post, which introduced MVC . Recall those sine qua non MVC requirements:
- Clouds are APIs
- Clouds are SOAs
- Clouds Hide Implementation
- Clouds are Fully Automated
- Clouds are Utilities
Every time a new, hot technology appears on the scene, many companies with old, boring technologies slap a sticker on the front of their product, proclaiming it to be a torchbearer for the new tech. It's something of a parlor trick. Certainly this has been the case with cloud technologies. As a result, there's a need to differentiate things that.
Several years ago, NIST produced documents (SP 800 145 & 146) that made admirable and compelling efforts to categorize cloud service offerings with the tripartite taxonomy already in use: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). NIST sought to tighten loose definitions. This was about as.
I've noticed recently that I'm getting quite a bit of grey in my beard. While there are many downsides to being an aging geek (I can't pull all-nighter coding sessions any more without hell to pay for several days), one of the benefits is gaining some perspective on how innovations play out over time. I started building software in the late '80s.
Cloud infrastructure services have allowed our field to gradually abstract computation tasks from long-standing physical restraints. As cloud infrastructure adoption increased, we realized the power and efficiencies of quick deployments and elastic scaling, giving birth to the DevOps movement. We've been steadily directing more of our attention.