A recent article by Scott Lowe, The CIO and the Cloud: Embrace, Extend, Innovate, got me thinking about how we have embraced both the cloud and the network to transform our enterprise IT practice at Juniper. Cloud has become a “very important arrow in our quiver”.
Like many other enterprises, Juniper IT set out a few years ago to modernize our application platform and migrate to the cloud. In 2010-2011 timeframe, we reviewed our apps portfolio and decided to migrate as much as we could to the cloud within a three-year time horizon. We started down our first phase of “cloud deployment” and in 2011 we successfully migrated to SalesForce.com.
In 2012, we evolved our thinking and decided not to limit ourselves to just cloud-based apps. Where it made sense, we asked ourselves the game-changing question: “Why Not Cloud?” In addition to using the cloud for our applications and purchasing software as a service (SaaS), we were eager to explore Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) as viable cloud services for IT.
In using the Why Not Cloud approach as a filter for pretty much everything, we significantly revamped our IT operations and accomplished the following in 2012:
Migrated Peoplesoft to an IaaS model, now managed by IBM’s SCE+ on a Juniper-based solution.
Evaluated a PaaS model to crush 150+ applications into one standardized platform.
Went from originally planning 10-15% in PaaS to now 55% PaaS.
Lowered total cost of ownership. Our best of breed approach could have grown into hundreds of little SaaS clouds. Instead, big chunks of apps were included within a single platform, so we ended up with fewer systems to manage (and also made the bits around the edge simpler).
Migrated email/calendaring to SaaS Office 365; Juniper is currently one of the largest multi-tenant deployments of Office 365
Re-designed our IT staff functions into three teams (apps/service, platform, and infrastructure) for both execution/delivery, mapping to Why Not Cloud.
Going forward, Why Not Cloud does not mean everything will/must go to the cloud. Rather, it is a statement of strategic intent for Juniper IT. There may be applications like critical R & D apps that we may never move to the cloud. But we are still leveraging the architecture and simplicity of the cloud design to set up private and hybrid clouds.
We’ll continue to use our Why Not Cloud strategy to adapt our Juniper IT practice--fully leveraging cloud-based resources over the Juniper network. Currently, we are prepping for a PaaS deployment that will collect 150+ enterprise applications and processes, consolidating them into one streamlined process that impacts the bottom line. Once this deployment is completed in 2014, we will be able to scale and double the size without adding unnecessary costs, and operate more efficiently, executing tasks at appropriate locations around the globe. We expect to consolidate more data centers and move “leftovers” to an IaaS model. Certain elements which have unique value to Juniper (and cannot be purchased in the general software marketplace) will be specifically reserved for an IaaS model.
Ultimately, for Juniper IT, we aim for a “zero” footprint data center, all Saas, PaaS, IaaS. And wherever possible, we will use a Juniper-based network with our X-aaS partners.Indeed,cloud has become a “very important arrow in our quiver”.