1.
Journey to Cloud Native
A Three Step Path to Modernizing Applications
Alois Mayr, Technology Lead Cloud & Containers
@mayralois

2.
The future is … now
bash-3.2$ cf target -s prod
API endpoint: https://api.cf.$DOMAIN
User: amayr
Org: dynatrace
Space: prod
bash-3.2$ cf push

3.
The cloud-native evolution
9 out of 10
of surveyed respondents are going to
migrate to cloud technologies
within the next five years
Get your copy https://info.dynatrace.com/apm_all_wp_cloud_native_evolution_en_registration.html

4.
..but what does it mean to be cloud native?
Container packaged - isolated unit of application deployment
Dynamically managed - central orchestration process
Micro-services oriented - loosely coupled, explicit dependencies
Source: Cloud Native Computing Foundation

5.
..but what does it mean to be cloud native?
Source: Pivotal.io

6.
..but what does it mean to be cloud native?
Onsi Fakhoui: VP Cloud Research & Development

7.
Bimodal IT
Not every project is a cloud project, but cloud thinking is everywhere

8.
Develop
Big monolithic application. Small interconnected purpose-built services.

9.
Pizza box teams
Small teams can deliver features into production

10.
You build it, you run it.
Werner Vogels, CTO Amazon
New rules in the game

11.
Ship
Deploy
Big Bang Releases of single special built applications. Small continuous service delivery of standardized delivery blocks.

12.
Compute
Hardwired datacenters. Datacenter as an API.

13.
We see three different stages how
companies embrace transformation
The journey to become cloud-native

14.
Stage 1: First steps into the cloud by CD
“Lift and Shift” to modern platforms
Applications stay the same
Release speed massively increases
Automation is key

15.
Writing fast cloud native applications
Rule #1: Don’t write slow code

16.
Control code complexity
N+1 interaction patterns - control flow design
More than 10 service hops - hard to debug
Highly asynchronous - hard to understand
Unusual Log Activity

17.
Continuous performance management

18.
Stage 2: Refactoring towards micro services
First micro services
Scheduling and orchestration
Architectures become polyglot
Independent release cycles

19.
Writing fast cloud native applications
Rule #1: Don’t write slow code
Rule #2: Don’t write code that doesn’t scale

20.
Control environment complexity
Service call payload - < 200 kb
Chatty services - > 50 service calls
Inter-tier heavy interactions - granularity and locality
Status codes - only OK is 200

21.
Understand micro service interactions

22.
Tightly coupled. Really Distribute?

23.
A whole new technology stack
Develop
Ship
Deploy
Run
Scale
Compute

24.
…may or may not have an
(immediate) impact to application
service performance
..lets you face new problems

25.
Stage 3: Dynamic micro services
Up and down scaling near real time
Advanced resilience mechanisms
Infrastructure totally abstracted

26.
Writing fast cloud native applications
Rule #1: Don’t write slow code
Rule #2: Don’t write code that doesn’t scale
Rule #3: Understand application behavior

27.
Watch your application live
Health monitoring – symptoms
Orchestration monitoring - causality
Application monitoring - root cause

28.
7:00 a.m.
Low Load and Service running
on minimum redundancy
12:00 p.m.
Scaled up service during peak load
with failover of problematic node
7:00 p.m.
Scaled down again to lower load
and move to different geo location
Deployments are no longer static

29.
You don’t fly by hand here
820 Billion
dependencies
Network Problem
Mushroom cloud effect

30.
Make monitoring part of your platform

31.
Make monitoring part of your platform

32.
Make monitoring part of your platform

33.
Thank you!
Alois Mayr
alois.mayr@dynatrace.com
@mayralois