Cloud Native Transformation

An Idea in the Morning, is Running in Production by the Evening

  • Why it Matters
  • What it Looks Like
  • How to Become Cloud Native
Why it Matters

Do your teams release software to production weekly, daily or every hour? Do you practice software development with tools, process and culture that can respond to the speed of market and customer changes? Agility allows you to experiment with new business models, learn from your mistakes and identify patterns that work. In every market, speed wins.

Cloud Native describes the patterns of high performing organizations delivering software faster, consistently and reliably at scale. Continuous delivery, DevOps, and microservices label the why, how and what of the cloud natives. In the the most advanced expression of these concepts they are intertwined to the point of being inseparable. Leveraging automation to improve human performance in a high trust culture, moving faster and safer with confidence and operational excellence. This is the cloud native advantage.

What it Looks Like

Developers may spin-up virtual machines and containers on their laptops in minutes, but that doesn't help if it takes a month to procure servers. There is a better way. Cloud Native organizations deliver by enabling fully automated self service deployment. Instead of dealing with VMs, containers or other infrastructure primitives, developers focus on the code.

Cloud Native means building reliable systems from unreliable components. Designing for failure means a cloud native approach must provide structured automation of components with predictable scaling and failure characteristics. This includes automation that embraces the realities of scale and the lessons of cloud native companies like Netflix and Amazon.

Finally, a cloud native approach rests on explicit contracts that are decoupled from the specifics of the underlying platform and it is these contracts that developers rely on. This is the promise of cloud native.

How to Become Cloud Native

The journey to cloud native for an enterprise should be guided by an understanding of the current state and goals. At Pivotal, we see our customers embarking on three types of journey - Greenfield Development, Legacy Management and IT Transformation.

Greenfield Development teams tend to be smaller companies or selected groups within a large company empowered to change. They typically have the freedom to experiment and start fresh developing net-new applications. Legacy Management teams have full portfolio of existing IT apps to maintain and operate under challenging constraints. Finally, IT Transformation groups are driven from top-down to bring organizational change for an entire portfolio of apps. Some organizations might have different groups optimizing for each of these leveraging a multi-modal IT strategy. Whether you are looking to get leverage from IT evolution or ready for an IT revolution, there is a Cloud Native path for you.