As the Enterprise Irregulars discuss in this blog the Cloud Native model is underpinned by early maturity model work, a journey that sees applications transform from a traditional to a fully Cloud-centric architecture:
I. Cloud Ready
A simple app that is Cloud ready by using basic Cloud services not its own file system.
II. Cloud Friendly
Begins to leverage platform more such as multi-zone High Availability and horizontal scalability, and is designed as a ‘Twelve Factor‘ app.
III. Cloud Resilient
Cloud agnostic, can work across multiple Clouds and can tolerate failure of underlying services.
IV. Cloud Native
A Microservice, API-driven architecture.
In this blog
and this Slideshare Nirmata define how their technology can be applied to implement this approach.
Cloud Native Competitive Advantage
Pivotal also reference the model in their presentation the Cloud Native Journey.
This sets the strategic context for the technologies, centred around the principle that the capabilities required for digital transformation can’t be bought, they must be developed in-house. As a consequence by 2020 75% of application development supporting digital business will be built not bought.
They describe a core enabling technology architecture of ‘Continuously Delivered Microservices’, showcasing example implementations such as the Spring Cloud Dataflow.
The principle business benefit is the ability to deliver new digital products, much faster than was previously possible.