This document discusses running applications in a cloud native way. It introduces Kaslin Fields as a cloud advocate at Oracle and CNCF ambassador. It then summarizes concepts like lift and shift versus cloud native applications, containerization using Docker containers and container registries, orchestration using Kubernetes, serverless/functions as a service, infrastructure as code using Terraform, monitoring with Prometheus, streaming and messaging with Apache Kafka, and events and functions triggered by events. The document aims to explain cloud native concepts and technologies using analogies to operating an amusement park.

1. Welcome to CloudLand
Kaslin Fields
Cloud Advocate
Oracle Cloud Infrastructure
Copyright © 2019 Oracle and/or its affiliates.
kaslinfields

2. Kaslin Fields
• Cloud Advocate at Oracle
• CNCF Ambassador
• Cloud Native, DevOps, Kubernetes
• Tech Comic Creator (https://kaslin.rocks)
Copyright © 2019 Oracle and/or its affiliates.

3. • “Lift and Shift”
• An application which has gone through a “Lift and Shift” has been moved
your datacenter to the cloud, but is still running in much the same way it was
your datacenter
• Cloud Native
• The cloud is a unique environment, with unique benefits
• Certain methodologies can only be used in the cloud due to its unique
– these capabilities and methodologies are called “Cloud Native”
3
VS
Twitter: @kaslinfields

4. Cloud Native Computing Foundation
(CNCF)
• Independent non-profit
• Mission: Promote the growth and adoption of Cloud Native
Technologies
• Support and promote many “cloud native” open source projects
• Maintain a “Cloud Native Landscape” to help companies understand
the breadth of Cloud Native software
4Twitter: @kaslinfields

5. 5

6. 6Twitter: @kaslinfields

7. What are the most exciting and
unique things about going to an
amusement park or festival?
7Twitter: @kaslinfields

8. Amusement Park / Festival Food
8Twitter: @kaslinfields

9. In-House vs Cloud Native
Copyright © 2019 Oracle and/or its affiliates.

10. Container Registries
10
• Convenient and Efficient Packaging
– Compatible Docker Registry
• Same Great Flavor Every Time!
– A container created from a container
image will always be the same – it’s
repeatable
• Portable
– Containers can run on many types of
Operating Systems.
• Examples: Harbor (CNCF)
Popcorn Kernels
Twitter: @kaslinfields

11. Container Orchestration - Kubernetes
11
• Delicious Fresh-Popped Popcorn!
– Use Container Images from a
Container Registry
• Share with your friends!
– Run containerized applications for
many teams on one Kubernetes
cluster
– The best tool for running containers
at scale
• Examples: Kubernetes! (There
are other tools but Kubernetes is
by far the leader)
Twitter: @kaslinfields

12. Serverless / Functions as a Service
12
• Pre-Popped, Pre-Candied, and Pre-
Packaged!
– “Serverless” lets you focus on the code
that’s important to your business, while
the infrastructure is abstracted away by
the serverless tool
• Conveniently Portioned!
– When using a Cloud service, pay only
while your code is running
• Examples: Fn Project
Twitter: @kaslinfields

13. Functions Use Case
13
Storage
1. Upload an image
3. Process Image
4. A processed image is
produced and stored.
2. The image being inserted to
object storage triggers an
event Twitter: @kaslinfields

14. Service Mesh
14
• Multiple Flavors on One Stick!
• The ”mesh” consists of many tools which
provide services needed to run Cloud Native
architecture
• A “One Stop Shop”
• Tools include proxies, monitoring, logging,
tracing, and more!
• A service mesh should be extensible, so you
can add any missing tools you need.
• Examples: Istio & linkerd (CNCF)
Twitter: @kaslinfields

15. Terraform: Infrastructure as Code
15
• Lots of ingredients in a convenient,
delicious package!
• Manage all your infrastructure resources in
various environments declaratively
• Made Fast!
• Create/manage many resources with a
simple command
• Terraform is owned by Hashicorp
• Other Infrastructure as Code tools exist,
butTerraform is a popular Open Source
one
Twitter: @kaslinfields

16. There’s more to an amusement park
than just food though.
17
Let’s talk about
some other things
that go into running
an amusement park.

17. Cloud Events
18
• Something Happened!
– Create a trigger which will send a
message (an event) to the endpoint of
your choice when a certain action occurs
• For example, a new object is inserted into object
storage
• Standardized
– Events are based on a standardized
format owned by the Cloud Native
Computing Foundation (CNCF)
Event
Event Receiver/
Endpoint

18. Functions + Event
Use Case
19
Storage
1. Upload an image
2. The image being inserted to
object storage triggers an
event
3. Process Image
4. A processed image is
produced and stored.
This trigger is
an event!

19. Monitoring
• Ride Status at a Glance
• Monitoring tools such as Prometheus
(owned by the CNCF) allow you to
keep an eye on the status of your
resources
• They collect data which can then be
displayed as graphs through
visualization tools
• Examples: Prometheus (CNCF),
Grafana
20
Ride Wait Time/Status
Ferris Wheel 15min
Spinning Tea Cups 25min
Speed Rider CLOSED
Viking Ship 10min
Twitter: @kaslinfields

20. Streaming & Messaging
• A Constant Stream of Data
• Running an amusement park, just like
running applications in the cloud,
produces constant data which must be
processed.
• Things like how many visitors usually
visited the park today?This data needs
to be stored somewhere and then
processed.
• Open Source tools can be used to set up
a pipeline to handle this stream of data.
• Examples: Apache Kafka, NATS
(CNCF)
21
Tickets
Twitter: @kaslinfields

21. 22
Thanks for Visiting Cloud Land!