Jerimar

1. CLOUD NATIVE AND
EMERGENT TRENDS
Chapter VI

2. Objectives
 Identify Cloud native and emergent trends
 Discussed the benefits/ Advantage and dis-advantages of
each trends

3. Overview
The trends in the cloud-native world confirm the
interest of companies. Thanks to cloud
infrastructures and cloud-native applications,
companies not only get the resources they need to
ensure a faster time-to-market of new projects, and
with an as-a-service mode, but they are also able
to integrate applications more easily, both with
each other and with third-party software and
services.

4. Emerging trends in cloud native
infrastructure

5. Emerging trends
2020 began a wide array of future-forward business
sectors adoption cloud solutions as the cornerstone
of the tech stacks. As many of such solutions are
being standardized and growing in compatibility, it
opens up a path for innovative channel roles to
support an application level process that combines
the incorporation of AI and machine learning with
high-performance computing.

6. 1. Hybrid Multi Cloud
 Hybrid implies something heterogeneous in origin or
composition. In other words, it is something that is composed
of multiple other things. Multicloud is pretty simple, and
refers to using more than one cloud computing service.
 So, when you use the term “hybrid” in conjunction with
“multicloud,” it implies an IT infrastructure that uses a mix of
on premises and/or private / public cloud from multiple
providers.
 This is a sensible approach for many organizations because
it enables you to maintain and benefit from the systems and
data that you have built over time. And, to couple it with
current best practices for reducing cost and scaling with
cloud services where and when it makes sense.

7. Hybrid Multi Cloud

8. 2. Server less
 Server less is a cloud execution model that enables a simpler,
more cost-effective way to build and operate cloud-native
applications.
 Server less offloads all management responsibility for backend
cloud infrastructure and operations tasks - provisioning,
scheduling, scaling, patching and more - to the cloud provider.
This gives developers more time to develop and optimize their
front-end application code and business logic. And with server
less, customers never pay for idle capacity. They pay only for
the resources required to run their applications, and only when
those applications are running.

9. What is Serverless?

10. Server less offers a number of individual
technical and business benefits; Pro’s
 Serverless enables development teams to focus on writing
code, not managing infrastructure
 Serverless customers pay for execution only.
 Serverless is a polyglot environment, enabling developers to
code in any language or framework - Java, Python, node.js.
 Serverless simplifies deployment and, in a larger sense
 Require parallel processing

11. Serverless offers a number of individual
technical and business benefits; Con’s
 Stable or predictable workloads
 Cold starts
 Monitoring and debugging
 Vendor lock-in

12. Microservices
 Microservices architecture is an approach in which a single
application is composed of many loosely coupled and
independently deployable smaller services.
What are microservices?
 Microservices (or microservices architecture) are a cloud
native architectural approach in which a single application is
composed of many loosely coupled and independently
deployable smaller components, or services.

13. How microservices benefit the
organization
 Microservices are likely to be at least as popular with
executives and project leaders as with developers. This is
one of the more unusual characteristics of microservices
because architectural enthusiasm is typically reserved for
software development teams.

14. Cloud Native
Explore cloud native applications and how they drive innovation and speed
within your enterprise
Cloud native refers less to where an application resides and more to
how it is built and deployed.
 A cloud native application consists of discrete, reusable components known
as microservices that are designed to integrate into any cloud environment.
 These microservices act as building blocks and are often packaged in
containers.
 Microservices work together as a whole to comprise an application, yet
each can be independently scaled, continuously improved, and quickly
iterated through automation and orchestration processes.
 The flexibility of each microservice adds to the agility and continuous
improvement of cloud-native applications.

15. Cloud Native

16. Cloud Native

17. Advantages and disadvantages
Advantages
 Compared to traditional monolithic apps, cloud native applications can
be easier to manage as iterative improvements occur using Agile
and DevOps processes.
 Comprised of individual microservices, cloud native applications can be
improved incrementally and automatically to continuously add new and
improved application features.
 Improvements can be made non-intrusively, causing no downtime or
disruption of the end-user experience.
 Scaling up or down proves easier with the elastic infrastructure that
underpins cloud native apps.
 The cloud native development process more closely matches the speed
and innovation demanded by today’s business environment.

18. Disadvantages
 Although microservices enable an iterative approach to
application improvement, they also create the necessity of
managing more elements. Rather than one large application, it
becomes necessary to manage far more small, discrete
services.
 Cloud native apps demand additional toolsets to manage the
DevOps pipeline, replace traditional monitoring structures, and
control microservices architecture.
 Cloud native applications allow for rapid development and
deployment, but they also demand a business culture that can
cope with the pace of that innovation.

19. What is application modernization?
 Application modernization is the process of taking existing
legacy applications and modernizing their platform
infrastructure, internal architecture, and/or features. Much of
the discussion around application modernization today is
focused on monolithic, on-premises applications—typically
updated and maintained using waterfall development
processes—and how those applications can be brought into
cloud architecture and release patterns, namely
microservices DevOps.

20. What is application modernization?

21. Why modernize legacy
applications?
 Legacy applications are also often monolithic applications.
Monolithic applications have two characteristics that make it
desirable to modernize them: they are difficult to update, and
they are difficult and expensive to scale.

22. Assignment
 Via Sedi