Cloud native is a new paradigm for developing, deploying, and running applications using containers, microservices, and container orchestration. The Cloud Native Computing Foundation (CNCF) drives adoption of this paradigm through open source projects like Kubernetes, Prometheus, and Envoy. Cloud native applications are packaged as lightweight containers, developed as loosely coupled microservices, and deployed on elastic cloud infrastructure to optimize resource utilization. CNCF seeks to make these innovations accessible to everyone.

1. Cloud Native and CNCF

2. From Virtualization to Cloud Native

3. What is Cloud Native?
• Cloud Native is a new paradigm (or modern way) to develop, deploy & run
applications using open source software stack.
• Cloud Native Application Design revolves around 3 concepts:
• Microservices
• Containers
• Container Orchestration
• Cloud native computing uses an open source software stack to:
• Segment applications into microservices,
• Package each part into its own container
• Dynamically orchestrate those containers to optimize resource utilization
• This new paradigm fully exploit advantages of cloud computing model
(means you will focus on how applications are created & deployed, not
where)

4. CNCF Cloud Native Definition v1.0
Cloud native technologies empower organizations to build and run scalable
applications in modern, dynamic environments such as public, private, and
hybrid clouds. Containers, service meshes, microservices, immutable
infrastructure, and declarative APIs exemplify this approach.
These techniques enable loosely coupled systems that are resilient,
manageable, and observable. Combined with robust automation, they allow
engineers to make high-impact changes frequently and predictably with
minimal toil.
The Cloud Native Computing Foundation seeks to drive adoption of this
paradigm by fostering and sustaining an ecosystem of open source, vendor-
neutral projects. We democratize state-of-the-art patterns to make these
innovations accessible for everyone.

5. Key Attributes of Cloud Native Apps
• Packaged as lightweight containers
• Developed with best-of-breed languages and frameworks
• Designed as loosely coupled microservices
• Centered around APIs for interaction and collaboration
• Architected with a clean separation of stateless and stateful services
• Isolated from server and operating system dependencies
• Deployed on self-service, elastic, cloud infrastructure
• Managed through agile DevOps processes
• Automated capabilities
• Defined, policy-driven resource allocation

6. Key Attributes of Cloud Native Apps
• Cloud-native applications are a collection of independent and autonomous
services that are packaged as lightweight containers. Unlike virtual machines,
containers can scale-out and scale-in rapidly. Since the unit of scaling shifts to
containers, infrastructure utilization is optimized.
• Each service of a cloud-native application is developed using the language and
framework best suited for the functionality. Cloud-native applications are
polyglot, services use a variety of languages, runtimes and frameworks
• Services that belong to the same application discover each other through the
application runtime. They exist independent of other services.
• Cloud-native services use lightweight APIs that are based on protocols such as
representational state transfer (REST), Google’s open source remote procedure
call (gRPC) or NATS. REST is used as the lowest common denominator to expose
APIs over hypertext transfer protocol (HTTP). For performance, gRPC is typically
used for internal communication among services. NATS has publish-subscribe
features which enable asynchronous communication within the application.

7. Key Attributes of Cloud Native Apps
• Services that are persistent and durable follow a different pattern that assures higher availability
and resiliency. Stateless services exist independent of stateful services. There is a connection here
to how storage plays into container usage. Persistence is a factor that has to be increasingly
viewed in context with state, statelessness and — some would argue — micro-storage
environments.
• Cloud-native applications don’t have an affinity for any particular operating system or individual
machine. They operate at a higher abstraction level. The only exception is when a microservice
needs certain capabilities, including solid-state drives (SSDs) and graphics processing units
(GPUs), that may be exclusively offered by a subset of machines.
• Cloud-native applications are deployed on virtual, shared and elastic infrastructure. They may
align with the underlying infrastructure to dynamically grow and shrink — adjusting themselves to
the varying load.
• Each service of a cloud-native application goes through an independent life cycle, which is
managed through an agile DevOps process. Multiple continuous integration/continuous delivery
(CI/CD) pipelines may work in tandem to deploy and manage a cloud-native application.

8. Key Attributes of Cloud Native Apps
• Cloud-native applications can be highly automated. They play well with the
concept of infrastructure as code. Indeed, a certain level of automation is
required simply to manage these large and complex applications.
• Cloud-native applications align with the governance model defined through a set
of policies. They adhere to policies such as central processing unit (CPU) and
storage quotas, and network policies that allocate resources to services. For
example, in an enterprise scenario, central IT can define policies to allocate
resources for each department. Developers and DevOps teams in each
department have complete access and ownership to their share of resources.
Source : https://thenewstack.io/10-key-attributes-of-cloud-native-applications/

10. CNCF – Cloud Native Computing Foundation
• CNCF is responsible for building sustainable ecosystems of Cloud
Native softwares
• CNCF serves as the vendor-neutral home for many of the fastest-
growing open source projects like Kubernetes, Prometheus, Envoy ,
etc.
• CNCF is part of the nonprofit Linux Foundation.
• Founded : December 2015
• There are many projects under CNCF Umbrella.
• CNCF Mission : Foster and sustain open source, vendor-neutral
projects around cloud native.

11. Big names on CNCF Memberships
More info : https://www.cncf.io/about/members/

12. CNCF Landscape and Projects
• CNCF Landscape: https://landscape.cncf.io/
• CNCF Projects Maturities:
• Graduated Projects (Early Majority)
• Incubated Projects (Early Adopters)
• Sandbox Projects (Innovators)

13. CNCF Graduated Projects
* Per 15 November 2019

14. CNCF Incubated Projects
* Per 15 Nov 2019

15. CNCF Sandbox Projects
… and a few more

16. CNCF and Cloud Native Propositions
• Cloud Native empowers organizations to build and run scalable distributed
applications in a modern and dynamic cloud environments
• By using containers, containers orchestration, service mesh, microservices,
etc
• Utilizing open source software stack : Kubernetes, Prometheus, Istio, etc
• Enabling robust distributed applications, resilient, manageable loosely
coupled systems
• Automation enables us to make high impact changes frequently and
predictably with minimal toil
• CNCF drives the adoption of this paradigm by fostering and sustaining
vendor neutral open source projects

17. Why Organizations are adopting Cloud Native
• For Better Resource Utilization
• For Multi-Cloud & Hybrid-Cloud Strategy
• For Modernization of Applications
• For Velocity & Agility - DevOps Practice

18. Learn More about Cloud Native and CNCF
• CNCF Trail Map:
https://raw.githubusercontent.com/cncf/trailmap/master/CNCF_TrailMap_lat
est.png
• CNCF Cloud Native Landscape :
https://landscape.cncf.io/
• CNCF Website :
https://www.cncf.io
• Indonesia Cloud Native Discussion Group :
https://t.me/microserviceid

19. Summary
• Cloud-native applications are specifically designed to run on cloud
infrastructure, hence the term ‘native’. They are growing in popularity
because they deliver benefits, which include: high availability and
responsiveness, plus also strong resilience and flexibility through
autonomous and self-healing capabilities.
• CNCF democratize state-of-the-art patterns to make these
innovations accessible for everyone.
• It’s not an option to not do open source. If we don’t get involved with
cloud native and take the lead, we will fall behind our competitors.

20. Learn More about Cloud Native Tech

21. Q and A