This document discusses cloud native applications and platforms. It defines cloud native applications as applications that do not require resilient infrastructure. It explains that to deploy and deliver applications reliably at scale, new requirements have emerged for programmability, elasticity, economics, and strong instrumentation and telemetry of the infrastructure layer. The document discusses different types of cloud native platforms and demonstrates examples using containers, microservices, and tools like Docker and Kubernetes.

1. 11
CLOUD NATIVE APPLICATIONS
CONTAINERS, MICROSERVICES,
PLATFORMS,CI-CD… OH MY!!
FABIO CHIODINI
CLOUD NATIVE APP | dotnext TEAM |DELL EMC
@FabioChiodini

2. 2
WHY ARE WE HERE?

3. 3
SOFTWARE IS TRANSFORMING INDUSTRIES

4. 4
ENTEPRISES ARE FOLLOWING

5. 5
CLOUD NATIVE APPLICATIONS
“Applications that do not require resilient infrastructure”
*
*Duncan C.E. Winn

6. 6
HOW DO THE TERMS FIT IN YOUR LIFE-CYCLE?
DESIGNDEPLOYMANAGE

7. 7
TO DEPLOY AND DELIVER APPLICATIONS RELIABLY, AT SCALE
RESULTING IN NEW REQUIREMENTS FOR IT

8. 8
• Programmability
(“Infrastructure As Code”)
• Elasticity (Which Demands
A Scale-Out Architecture)
• Economics (Steers Towards
Standard Servers +
Software)
• Strong Instrumentation
And Telemetry Of
Infrastructure Layer
CLOUD NATIVE PLATFORM REQUIREMENTS
SELF HEALING | MULTI-CLOUD SUPPORT
INTEGRATED LOGGING
APPLICATION PERFORMANCE MANAGEMENT
SELF SERVICE | POLYGLOT LANGUAGE
AUTO SCALING | CONTAINER MANAGEMENT

9. 9
BTW…
CONTAINERS vs VMs
101

10. 10
CLOUD NATIVE PLATFORM, IAAS AND CONTAINERS
Hardware
Virtual Machine
Container
Provisioning layer
Orchestration layer
Platform
I’m a
PaaS/Cloud
Native Platform
No, you’re
NOT
Cloud
Native
Platform
IaaS
Re-adapted from @swardley (Simon Wardley)

11. 11
DEMO #1
POWER OF CNAs
[AKA CNP DO-IT-YOURSELF]

12. 12
AN APP STORY… IN MICROSERVICES
Receiver
(receiver.py)
Honeypot #1
(honeypot.py)
Honeypot #2
(honeypot.py)
Honeypot #N
(honeypot.py)
Visualization Layer
Geolocation
Enrichment
Persistency
A Honeypot is a computer security
mechanism set to detect, deflect, or, in some
manner, counteract attempts at unauthorized
use of information systems
Honeypots
Provisioning
(Shell Script)

13. 13
Infra as Code
Service Discovery
AN APP STORY… OVER MANY CLOUDS + TOOLS
Honeypots
Provisioning
Receiver
(receiver.py)
etcd
Honeypot #1
(honeypot.py)
Honeypot #2
(honeypot.py)
Honeypot #N
(honeypot.py)
Visualization Layer
Agility
Scale Out
Consul

14. 14
Service Discovery
AN APP STORY… WITH MANY TOOLS
Honeypots
Provisioning
Receiver
(receiver.py)
etcd
Honeypot #1
(honeypot.py)
Honeypot #I
(honeypot.py)
Honeypot #2
(honeypot.py)
Honeypot #J
(honeypot.py)
Docker
Swarm
Master
Opens

15. 15
IN OTHER WORDS…
GOAL: Continuous Delivery
WHAT: Cloud Native Apps
HOW: Cloud Native Platform
THROUGH: DevOps Culture

16. 16
IN OTHER TWEETS

17. 17
HOW CAN
YOU
APPROACH IT?

18. Standardized
Built-in Availability and Security
Automate & Simplify Operations
Many Applications
Buy-focused
TWO TYPES OF CLOUD NATIVE PLATFORMS
Ultra-Flexible
Multiple Configurations
Platform = Core Competency
Few Applications
DIY-focused
STRUCTUREDUNSTRUCTURED
How many apps
in the enterprise?
MANYFEW
Is the platform
a core competency?
NOYES
PRESCRIPTIVEASSEMBLED

19. TWO TYPES OF INFRASTRUCTURES TO BUILD ON
Is racking, stacking, and
automating a core competency?
NOYES

20. 20
LET’S SEE HOW A
STRUCTURED PLATFORM
LOOKS LIKE

21. 21
DEMO #2
THE STRUCTURED EXPERIENCE
[AKA cf push tc]

22. 22
Scripts +
Docker Machine
+
Scripts
Service
Discovery
Docker
Swarm
PRESCRIPTIVEASSEMBLED
gorouter
CloudController
Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
Garden
etcd
Core
Services
Auth
Logging
Staging
Load Balancing
Containers
Management/
Scheduling
/HA
*In RED all the functions that I should have implemented *In GREEN all the added value of a proper Cloud Native Platform

23. 23
IN ESSENCE..
WHICH ARE THE LAYERS
IN THIS NEW WORLD?

24. 24
Cloud
Native
Platform
Hypervisor/
Abstraction
layer
IaaS/
Stack
Managers
LAYERS FOR CLOUD NATIVE APPLICATIONS
Manual Processes or Automation
vSphere/KVM/etc
*DIY= Do IT Yourself
Structured or Unstructured
Hardware K

25. 25
Hypervisor/
Abstraction
layer
vSphere/KVM/etc
BUILD BUY
IaaS/
Stack
Managers
Cloud
Native
Platform
HOW TO SIMPLIFY CNAS DEPLOYMENT
CONSUMEMANTAIN
Manual Processes or Automation
*DIY= Do IT Yourself
K
Structured or Unstructured
Hardware
Cloud Native
Stack Manager
STRUCTURED
Platform for CNAs
CI/HCI
Infrastructure

26. 26
RECAP / CLOSING COMMENTS
◊ Clear and Solid Business Needs for
Cloud Native Apps
◊ Many Tech/options to choose from
◊ Structured approach offers many
advantages
◊ Purpose built and
Simplified Infrastructure
can definitely help
Check OUT PCF Dev for your Labs

27. 27
THANK YOU!!!