DigiTalk Oktober 2017, München: Vortrag von Josef Adersberger (@adersberger, CTO bei QAware).

1. Cloud (Native) Computing
Dr. Josef Adersberger, QAware

2. 3

3. 2002
3
shoppen
registrieren
kaufen
Services

4. 2008
4
mehr
Services

5. 2011
5
mehr
Services

6. Bad News
6
§ “[…] it was unable to scale for 6 million pageviews per minute and was down
for most of the day during peak events.”
§ “This is the multi-million dollar question which the IT Department of Walmart
Canada had to address after they were failing to provide to their users on Black
Fridays for two years in a row.”
https://blog.risingstack.com/how-enterprises-benefit-from-microservices-architectures
Walmart auf http://www.oneops.com
Sehr lange
Release-Zyklen
Mangelnde
Skalierbarkeit

7. 2016
7
Additional
Services

8. Good News
8
Walmart auf http://www.oneops.com
“They wanted to prepare for the world by 2020, with 4 billion people connected, 25+
million apps available, and 5.200 GB of data for each person on Earth.
Walmart replatformed […] with the intention of achieving close to 100% availability with
reasonable costs.”
https://blog.risingstack.com/how-enterprises-benefit-from-microservices-architectures
§ “In fact, the organization reports thatsome 3,000 engineers […] drive 30,000
changes per month to Walmart software.”
§ “Those new applications,which span everything from mobile devices to the
Internet of things (IoT), are crucial weapons in a global e-commerce contest
that pits Walmart againstthe likes of Amazon and Alibaba,as well as a host of
other rivals that are emerging as the cost of entry into the online retail sector
continues to decline in the age of the API economy.”
http://www.baselinemag.com/enterprise-apps/walmart-embraces-microservices-to-get-
more-agile.html
§ “The Walmart […] servers […] were able to handle all mobile Black Friday
traffic with about10 CPU cores and 28Gb RAM.”
§ “On Thanksgiving weekend,Walmartservers processed 1.5 billion requests
per day. 70 percent of which were delivered through mobile.”
http://techcrunch.com/2014/12/02/walmart-com-reports-biggest-cyber-monday-in-
history-mobile-traffic-at-70-over-the-holidays
1000 deployments a day …
… triggered by dev teams.
~ 100% availability
resource efficiency
suitable scalability
enabled new kinds of
applications ( IoT, mobile, APIs)
to compete globally

9. 9
19.10.2017 - Google Search “walmart online success”

10. 3
WHAT DID THEY DO?

11. #GIFEE Google’s
(and Facebook’s, Twitter’s, Airbnb’s, ...)
Infrastructure
For
Everyone
Else

12. SPEED
(continuous delivery & devops)
ANTIFRAGILITY
(resiliency & autonomy)
HYPERSCALE
(traffic, data, features)
OPEX SAVINGS
(utilization & automation)
CLOUD NATIVE APPLICATIONS
DISRUPTINDUSTRIALIZE

13. PACKAGED AND
DISTRIBUTED AS CONTAINERS
BUILD AND COMPOSED
AS MICROSERVICES
DYNAMICALLY
EXECUTED IN THE CLOUD
CLOUD NATIVE APPLICATIONS
3KEYPRINCIPLES

14. BUILD AND COMPOSED
AS MICROSERVICES

15. Teile und herrsche
15

16. • Planning unit
• Team assignment unit
• Development unit
• Integration unit
Komponenten entlang des Software-Lebenszyklus
16
DESIGN BUILD RUN
Design Components Dev Components Ops Components
• Complexity unit
• Data integrity unit
• Cohesive feature unit
• Decoupled unit
• Release unit
• Deployment unit
• Runtime unit
• Scaling unit
?:11:n

17. 17
System
Subsystem
Komponenten
Services
Monolith
Macroservices
Microservices
Nanoservices
Good starting point
Dev Components Ops Components?:1
Decomposition Trade-Offs
+ Independent releases, deployments, teams
+ Runtime isolation (crash, slow-down)
+ More flexible to scale
+ Higher resources utilisation
- Distribution debt: Latency
- Increased infrastructure complexity
- Increased troubleshooting complexity
- Increased integration complexity

18. PACKAGED AND
DISTRIBUTED AS CONTAINERS

19. 19
“Verpackung” für Ops Components
Standard-Schnittstellen für Standard-Betriebsprozeduren
Einfach zu transportierende, schnell zu startende und mit
wenig Overhead ausführbare Software-Einheiten

20. DYNAMICALLY
EXECUTED IN THE CLOUD

21. Die 5 Gebote der Cloud.
1. Everything Fails All The Time.
2. Focus on MTTR and not on MTTF.
3. Respect the Eight Fallacies of Distributed Computing.
4. Scale out, not up.
5. Treat resources as cattle, not pets.
21

22. 22
Application Platform Cloud Native App
Cluster Orchestrator Applications
Cluster Scheduler Containers
Cluster Virtualization Cluster Resources
CaaS
Abstrahiert von
Infrastruktur im
Cluster
Verwaltet
Ressourcen für
die Ausführung
von Containern
Führt
Applikationen
auf dem
Cluster aus
PaaS
Stellt Ablauf-
und
Entwicklungs-
Umgebung und
APIs für Apps
bereit
IaaS

23. Application Platform Cloud Native App
Cluster Orchestrator Applications
Cluster Scheduler Containers
Cluster Virtualization Cluster Resources
CaaS
PaaS
IaaS
23

25. „There ain’t no such thing as a free lunch.“
Robert A. Heinlein, 1966, The Moon Is a Harsh Mistress

26. Keine Magie. Aber komplexe Technologie.
• Die Umsetzung von Systemen als Cloud Native Applikationen bringt gerade für kundennahe
Systeme wichtige Vorteile: Hyperskalierbarkeit, Antifragilität, Speed und Opex-Einsparungen.
• Cloud Native Applikationen sind in Microservices geschnitten, in Container verpackt und
laufen auf einem Cloud Native Stack.
• Cloud Native Applikationen sind hochgradig verteilte Systeme. Solche zu entwickeln ist
weiterhin eine Herausforderung.
• Der Cloud Native Stack macht die Komplexität beherrschbar. Die Technologien sind noch jung.
• Die hohe Abstraktion ist Segen und Fluch zugleich. Entwickler und Architekten brauchen
zusätzliche Skills und Know-How in etlichen neuen Technologien. Darum: jetzt beginnen.
26

27. 27

28. 28 http://www.qaware.de/news/java-magazin-cloud-native-universum

29. #adersberger
josef.adersberger@qaware.de
https://www.qaware.de
https://slideshare.net/qaware
https://github.com/qaware
&