Cloud Native

Developmen
t
Source- mu-stack.com
Key Contents
1.Introduction
2.How do you build cloud
native applications?
3.Cloud Native Apps vs.
Traditional Enterprise
Apps
4.Benfits Of Cloud
Native development
5.Conclusion
 INTRODUCTION
m
Source- mu-stack. co

A strategy to creating and executing apps known as "cloud native"

makes use of the benefits of the cloud computing delivery
mechanism.
B usinesses that create and run their apps utilising a cloud native
architecture do so more quickly and in response to client requests. Both
public and private clouds are suitable for cloud native development; the
key is to focus on how rather than where applications are built and
deployed.

SSoouurccr ee--mmuu-ss-taat
 How do you build cloud
native applications?
m
Source- mu-stack. co

DevOps - The purpose of DevOps is to deliver high-quality software that

addresses consumer concerns by working together with IT operations.
Software development, testing, and release occur more quickly, often, and
consistently in environments created by D evOps.
Microservices - A collection of small services, each of which implements a
business capability, operates within its own process, and communicates with
the others via HTTP APIs or messaging, is referred to as a microservice.
Since each microservice can be independently delivered, updated, modified,
and restarted from other services within the same application, usually as
part of an automated system, rapid upgrades to live applications are
possible without having an adverse effect on users.

Source- mu-stack.com
 How do you build
cloud native
m
Source- mu-stack. co

applications?
Containers - Compared to traditional virtual machines, containers offer both
efficiency and speed (VMs). A single O S instance is dynamically split into one
or more isolated containers using operating-system-level virtualization, each of
which has its own writable file system and resource allotment. Containers are
the perfect computing vehicle for deploying lone microservices due to the low
overhead of building and destroying them and the great packing density in a
single VM.

Source- mu-stack.com
 Cloud Native Apps vs. Traditional
Enterprise Apps
m
Source- mu-stack. co

CLOUD NATIVE APPS TRADITIONAL ENTERPRISE

APPS
Predictable - The "contract"
or architecture that cloud This kind of application frequently
native programmes adhere takes longer to develop, delivers
to is intended to maximise
updates in large, irregular batches,
resilience through
predictable actions. The way scales in rather than out, and
software is built is dictated presumptively ensures high availability
by the automated, of dependent services.
container-driven
infrastructure found in cloud
platforms.

Source- mu-stack.com
 Cloud Native Apps vs. Traditional
Enterprise Apps
m
Source- mu-stack. co

CLOUD NATIVE APPS TRADITIONAL ENTERPRISE

Right-sized capacity - When an APPS
application is deployed, resources are Oversized capacity - Traditional IT
dynamically allocated and reallocated delays the launch of an application by
based on the requirements of the creating a special, specialised
application via a cloud native
infrastructure solution (a "snowflake")
application platform, which automates
for it. With minimal potential to scale
infrastructure provisioning and
beyond design restrictions to meet
configuration. Building on a cloud native
demand, the solution is frequently
runtime improves application lifecycle
oversized and constructed to satisfy
management, including scalability to
meet demand, resource utilisation, worst-case capacity predictions.
orchestration across available
resources, and failure recovery with
little to no downtime.
Source- mu-stack.com
 Cloud Native Apps vs. Traditional
Enterprise Apps
m
Source- mu-stack. co

CLOUD NATIVE APPS TRADITIONAL ENTERPRISE

APPS
Independent - Applications are
divided into small, loosely linked, Dependent - Monolithic designs
independently operating services combine a variety of dissimilar
using a microservices services into a single
architecture. These services deployment package, which
enable frequent updates, scaling,
results in unneeded
and failover/restart without
dependencies between
affecting other services and map
services and reduces
to smaller, independent
development teams. development and deployment
agility.
Source- mu-stack.com
 Cloud Native Apps vs. Traditional
Enterprise Apps
m
Source- mu-stack. co

CLOUD NATIVE APPS TRADITIONAL ENTERPRISE

Rapid recovery - A dynamic, high- APPS
density virtualization overlay, Slow recovery - Due to higher
perfectly suited to the startup and shutdown times and
microservices architecture, is operating system overhead for
provided by the container runtime each VM, VMs by themselves
and orchestrator. In order to allow are a slower and less effective
elastic scaling and recovery/restart
foundation for microservice-
in the event of app or infrastructure
based systems.
failure, orchestration dynamically
coordinates the placement of
containers across a cluster.

Source- mu-stack.com
 Benefits of Cloud Native development
m
Source- mu-stack. co

COST EFFICIENCY FASTER DEPLOYMENT SECURITY

Cloud services only charge Go from concept to The cloud service provider
for necessary storage space implementation within a short follows industry-leading
and feature sets required span of time by dividing the security regulations such as
for your application application into descrete parts HIPPA, PCI DSS and ISO
development model. This using microservices. These can 27002. This ensures your
pay-as-you-go system then deployed into different application is protected
ensures lower costs and environments without worrying against data breaches,
higher profits. about the dependencies required. network and DDoS attacks.

Source- mu-stack.com
 Benefits of Cloud Native development

AVAILABILITY AND
m
Source- mu-stack. co

SERVER-LESS RESILIENCY
SCALABILITY
B y opting for a serverless Cloud Native applications are The cloud service provider
application the developers designed in such a way that they follows industry-leading
no longer have to worry don’t go offline even if there’s security regulations such
about networks, security, an infrastructure outage. These as HIPPA, PCI D S S and
and scalability of the fault tolerant applications are ISO
servers that run behind
capable of detecting uncertain 27002. This ensures your
the scenes.
issues like overload of requests, application is protected
These servers are owned
hardware failures, network against data breaches,
and maintained by service
providers reducing the connective errors, etc. network and DDoS
Total Cost of Ownership attacks.
(TCO) of the application.
 Conclusion
m
Source- mu-stack. co

A hybrid cloud involves mixed-hybrid computing, storage, and service

environment that combines on-premises infrastructure, private cloud
services, and a public cloud, with orchestration between the platforms. As
the world has gone remote, there is an increasing demand for applications
that are highly available around the globe.

Source- mu-stack.com
m
Source- mu-stack. co

Thank you!
mu-stack.com