Cloud Native Development- A strategy to build and run applications utilizing Cloud Computing

1. Cloud Native
Development
Source- mu-stack.com

2. 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

3. A strategy to creating and executing apps known as "cloud native"
makes use of the benefits of the cloud computing delivery mechanism.
Businesses 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.
INTRODUCTION
S
S
o
o
u
u
r
c
r
c
e
e
-
-
m
m
u
u
-
s
-
s
t
a
t
a
c
c
k
k
.
c
.
c
o
o
m
m
Source-
mu-stack.com

4. 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 DevOps.
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.
How do you build cloud
native applications?
Source-
mu-stack.com
Source-mu-stack.com

5. Containers - Compared to traditional virtual machines,containers offer both
efficiency and speed (VMs). A single OS 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.
How do you build cloud
native applications?
Source-
mu-stack.com
Source-mu-stack.com

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

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

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

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

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

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

12. 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.
Conclusion
Source- mu-stack.com
Source-
mu-stack.com

13. Thank you!
mu-stack.com
Source-
mu-stack.com