Cloud native… What does it mean to you? Chances are it means something different to the person next to you. Depending on the context it can mean very different things. Puzzled? Well, read on to understand the different contexts under which it is discussed and used.
Although there are lots of different opinions, in my experience generally people fall into one of two categories when the term is mentioned.
The first category is typically people focussed on public cloud who always refer to technical services “native” to public cloud such as AWS CloudFront, or Azure Traffic Manager. Services that are provided as part of the public cloud service, or definitively, something that can only be provided by [public] cloud.
People in this category typically do not consider virtual servers to be cloud native in this context.
Those falling in the second category consider Cloud Native is an approach to developing applications for the benefit of the enterprise and the users.
It does this by giving development teams the autonomy to adopt the most appropriate tools, technology and techniques across infrastructure and development for the sole purpose of accelerating bug fixing and feature release. In essence, it’s all about speed balanced with safety (application stability) in order to gain or keep a competitive edge.
Sounds awfully like DevOps, no? Well, yes, that’s because DevOps is part of Cloud Native. A key thing to understand though is that Cloud Native is only really relevant to applications designed to use microservice architecture.
Also in this context “Cloud” can be private, public or hybrid.
Cloud native are services that are native to public cloud infrastructure such as Azure Firewall, or an Azure VNet.
Cloud Native is a method of developing apps at speed that use microservice architecture located on public or private cloud.