“The Cloud” sounds like a mysterious and mystical place beyond reach and for that reason, and like so much business jargon, it is an overused term. People throw the term around without actually specifying what they mean. There are actually many types of clouds, in the sky and in computing. For private cloud computing, people need start defining exactly what service they are talking about. Even within the private cloud, there are different categories and Platform as a Service (PaaS) is one such sub-cloud. No longer will anyone look to the sky and see white fluffy cotton floating around.
The PaaS layer of the private cloud provides an agile, self-service, consumption-based resource which allows for sharing on an internal customer data center. This platform provides templates and tools which companies use to automate many processes that are usually done manually. Development and operations (DevOps) and administrators are then able to move quickly and more efficiently with fewer errors in creating custom applications or making changes. As previous methods have only resulted in wasted resources and a lack of centrality, DevOps is in need of a fresh approach.
Cloudy days
Everyone running middleware has the same challenges when starting projects. Developers need to be able to push out code frequently with small changes as the project progresses. They must perform this continually, and the changes eventually accumulate until the operations side experiences a bottleneck. Given the frequency with which code is being pushed out, operations teams are not able to support the developers. Projects are then halted or stopped, and money and time is lost.
Clouds and clear skies: a contradiction?
The benefits of the private cloud ultimately help to accelerate the benefits of DevOps and come at it from a different angle. The TIBCO Silver Fabric approach to DevOps limits the friction. As programmed code and changes can be pushed out in a controlled manner, companies like Qualcomm are able to build environments on the fly, thereby retaining agility and flexibility while keeping bottom line costs down.
However, that is also the crux of an unfamiliar contradiction. People want the best, but that usually means they will have to pay top dollar in order to get it. The private cloud is a lean initiative which ends up reducing costs over time with improved processes and services. Even IT departments that are not funded adequately can find salvation in such a minimally disruptive, cost-effective solution. Quality of service improves, and it’s cost beneficial. That’s a win-win, and cloudy days aren’t so gloomy with that kind of Silver lining.
To learn more on private cloud, watch the On-Demand webinar “From Virtualization to Private Cloud” featuring Forrester Research.
Good luck changing the misuse of cloud. You lost me at Paas.
Rubbish. More double-speak, e.g., “Development and operations (DevOps) and administrators are then able to move quickly and more efficiently with fewer errors in creating custom applications or making changes.”
Applications will not contain less errors owing to the implementation on PaaS but rather the adoption of the Agile development method that which is NOT a software product.
Furthermore, in enterprises that exist to develop applications, such as Qualcomm, as opposed to the converse, Operations rarely plays a role in managing the build / deploy / test environments thus this statement “Given the frequency with which code is being pushed out, operations teams are not able to support the developers.” is misleading at a minimum.
Just 5 questions. What happens with the information “in the cloud”? It’s really still mine? Can it be accessed, copied by the cloud managers and sold? Can it be manipulated? Can it be used, let’s say, to buy some stock in my company knowing beforehand about a merger?
I would like to add my thanks to the frey. The problem is technology acronyms are more vogue and frequent than finding their true definitions. Those on the ground in the mud understand the terms from a practical perspective, but most users are not in that psyche. So, you have entire conversations with 2 verbs, 3 adjectives and 98% acronyms making it sound like a foreign language. We need more clarifications about exactly what these terms mean and it would go a long way into turning conversations into communication rather than a cacophany of cute techie terms that means disparate things to participants in the conversation.
I appreciate this discussion very much. As a recruiter, working with various companies on their Dev Ops roles, it can be challenging to articulate what my client companies are working on without sounding “canned”.
Rima
Rima@well.com
Great post. I was checking constantly this blog and I’m impressed! Very useful info particularly the last part
I care for such info much. I was seeking this certain info for a long time. Thank you and good luck.