Hybrid IT sounds like Hybrid Cloud, which is a 3rd kind of “Not quite private, not quite public” cloud your IT team builds. It’s not. Hybrid IT is a strategy that gives IT flexibility to meet a range of business needs.
We hosted a recent webcast with Dave Bartoletti at Forrester Research who explained that “Hybrid cloud is a thing you manage, not something you build.”
He’s on the right track. The business doesn’t necessarily want IT to build anything. What the business wants is flexibility to quickly and cost-effectively deploy technology-based solutions that enable various strategic initiatives.
The sentiment is captured in a quote from executive panel at EMC World last year.
“I want to be able to tell our business units, ‘If you want to stand up services on the private cloud, go ahead. We have the technologies and the operating processes to do that. And when it’s time to move appropriate workloads to a public cloud, we have the technologies and the operational processes to do that too.’”
– Eric Craig, CTO, NBC Universal
So in other words, Hybrid IT is a flexible service delivery strategy that puts the right work in the right environment directed based on business need. That business need could be primarily speed of deployment, rapid scalability, or performance, or cost, or security.
Interesting data from recent survey by SolarWinds shows only ~10 percent of IT managers surveyed have not migrated any infrastructure at all to the cloud, while 10 percent feel they are likely to go “all-in” to cloud. Between these two poles are “The hybrid hordes” – the great mass of 80% of enterprises who intend to rely on both on-premises and cloud resources according to @JoeMcckendrick writing for Forbes.
With a Hybrid IT strategy, some IT services will be delivered via a datacenter built and managed by IT. Other services may be delivered by dedicated rack or even hosted private cloud via hosted service provider. Other delivered via public cloud. IT is in the middle acting as a central service consumption hub for all IT and other sourced services.
In the current business environment, most of the time speed matters most. Launching a new product, updating a business process, getting a new view on complex data to make an informed business decision — these improvements are time sensitive. And the improvements are usually delivered via applications that users rely on to execute tasks. So application and feature velocity matters a lot. And cost is always a consideration.
Why not application-centric?
So why are most Cloud Management Platforms infrastructure-centric instead of application-centric like CliQr CloudCenter? Developers want to focus on the customer problem and building better software. Not learning cloud APIs and nuances of infrastructure orchestration.
CloudCenter customer Prakash Iyer, VP Application Strategy at Trimble Technologies explains in a recent webcast, that they wanted a standard set of infrastructure services that developers can tap, whether delivered via datacenter or cloud. They wanted visual modeling of deployment blueprints, instead of scripting or orchestration workflow.
Their results based on using CloudCenter to focus developers on the application instead of the infrastructure, were impressive. They shifted application feature updates from twice yearly, to continuous delivery on demand, and reduced new product development lifecycle from 16 to 12 months.
Drop the mic!
Read this whitepaper to find out how you can get the Application-Centric Advantage with CliQr CloudCenter.