The Cure for the Common Cloud
Let’s face it. There’s a lot of hype around “the cloud.” Lots of promises, lots of claims, lots of vendors, and lots of lackluster results. All the while, software engineers and architects are getting sick of it.
If you’re a software engineer or architect, what does the cloud do for you? It’s elastic and infinitely scalable, so you just put your app up there and everything magically works, right? The cloud solves all of your scalability challenges, all of your app delivery challenges, and it just plain works, right?
Wrong. You’re the one responsible for building the software that the cloud exists to host and deliver, and you know full well that there’s a lot more to it than that.
What about onboarding new customers or business units to your app? The individual end-users – how do they get access, and to what are they entitled? What about charging for different features, or different transactions? What about managing the application lifecycle, and rolling out updates? What about the underlying architecture to make use of the cloud in an intelligent way? To actually take advantage of the raw compute power at your disposal, and not just use the cloud like it’s the late 90′s again and people are throwing their apps online like it’s going out of style.
These are the types of things that software engineers and architects are thinking about.
Haven’t we been through this before?
There are many significant engineering challenges associated with building and delivering applications today. This is very similar to when we first started developing applications for the desktop PC. Back then, everyone wrote code to manage memory, to interface with specific hardware, etc. Then the desktop OS came along, and made all of that complex and time consuming (but CRITICAL) work a thing of the past.
While the challenges themselves were different, they were still challenges that were specific to the delivery method, rather than challenges associated with building the actual software functionality. Those challenges will always be there, because the passion to innovate and develop applications that help facilitate better business performance, and meet the needs of end users is what drives great engineers/organizations. HOWEVER, the challenges associated with the delivery method/paradigm go away in time, as layers of abstraction come about to solve those problems for us.
The “Cure for the Common Cloud” is Here
Now let’s get back to today. Shouldn’t we expect that all of these challenges associated with building and delivering next generation software applications in this new cloud era will become a thing of the past? Won’t we be able to focus on building great software again, and not worry about all of the complexities of the delivery method? Someday? Maybe?
Yes. We can today!
A large and increasing number of organizations and developers have discovered the “Cure for the Common Cloud“. They’ve found the abstraction layer that handles all of the complex engineering challenges associated with building and delivery applications today, and truly leveraging private or public cloud infrastructure in an intelligent way. They’ve found the one technology that decouples apps from infrastructure, developers from IT/Operations, and business execution from IT implementation.
The Cure for the Common Cloud is here. Do you have it?