This document summarizes a presentation about cloud computing trends and the hype cycle. It discusses both the promises and fears around cloud adoption, as well as going through each stage of the hype cycle from the technology trigger to peak expectations to disillusionment to productivity. Key points discussed include the responsibilities that shift between on-premise, IaaS, PaaS and CaaS models, challenges around integration, resiliency, reversibility and vendor lock-in, and the importance of people and processes over just technology. The conclusion emphasizes the need for subtle choices around balancing control and outsourcing as well as periodically reassessing one's cloud strategy as the landscape evolves.

1. #APIdaysParis
☁-computing
We went through every steps of
#hypecycle
Shall we debrief ?
Adrien Blind, Ludovic Piot

2. starring…
Adrien Blind
@AdrienBlind
Devops Evangelist,
Docker Captain
Ludovic Piot
@lpiot
Head of
DevOps/Cloud unit

3. Introduction
Introduction
Cloud, bullshit bingo !

4. Every hopes!
Time-to-Market
accelerator
economic
Auto-magic
maintainance
security
performance
versatility
agile
automation
resiliency
With an even better offspring: #serverless

5. Every fears!
vendor
lock-in
Cloud-providers
spy your business
security
data privacy
deregulated
dev playground
death of
operation guys

6. A real market trend!

7. A real market trend!

8. Private cloud - an heterogeneous mkt
Many solutions…
… and as many definitions of what we
call private cloud computing
❏ virtualization,
❏ PaaS,
❏ Code to Prod integrated solution
❏ Infra as Code
2015 seems to be a loooong time ago.
Is CaaS changing the game?

9. Here comes the hype cycle

10. Technology trigger

11. Technology triggers

12. What do you really want?
On demand
Pay as you go
Elastic
Deliver a way we don’t know how to
in the on-premise legacy world
Time-to-Market
accelerator
security
performance
Available
everywhere
agile
resiliency

13. Challenge the legacy status quo?
Cloud computing is a
tremendous opportunity to
challenge how things exist in
the legacy world:
❏ Black vs. white wire
❏ Ops dpt is challenged
❏ Economically speaking
❏ operationnally speaking
❏ Green field
❏ On-demand provisionning
❏ Elasticity

14. First expectations
Wrong start with Google
App Engine…
… and as many definitions of
what we call private cloud
computing
❏ pricing model too mature for
consumers
❏ few runtimes available
❏ Vendor lock-in on data (BigTable)
❏ only Cloud-native apps
❏ No “pet” way for ops

15. Peak of inflated expectations

16. ❏ Pay-per-Use / CAPEX vs. OPEX
= cheaper / no longer investment
Really?!
❏ Autoscaling
= app adapts itself to its workload
Automagically?!
❏ High availability
= app hosted in the Cloud are unbreakable
Without any change?!
Then marketing inflated expectations

17. Trough of disillusionment

18. ❏ Pay-per-Use / CAPEX vs. OPEX
= you pay what you ask for NOT what you effectively use
Only advantage is the no-engagement thing
❏ Autoscaling
= you can script out/in-scaling following monitoring rules
Application has to be designed to behave correctly
❏ High availability
= multi-regions infrastructure have SLAs
Rest of HA is driven by your own software fail-over design
Desillusions!

19. Who’s responsible
On-premise Iaas Paas Caas
RESPONSIBILITIES
▪ Cloud provider
▪ Ops / hoster
▪ Dev / Client
PROPERTY
Cloud platforms may belong to
many client teams.
Platform governance is a
thing.
Hypervisor
VM
OS
Libs
conf.
Kernel
HDW
Middleware
conf.
Apps
conf.
Server Storage
Network
Logs / Metrology / Backups
Data
Runtime
conf.
Container
conf.

20. ❏ Requires different skills
❏ Cloud vendors try to attract directly Dev
people: NoOps myth, shadow IT…
❏ Assumes consumers to be autonomous
❏ Here come DevOps ;)
From cases to APIs

21. Ride the raging bull
Cloud services are often
proprietary (no source code
available).
You have to master
❏ how they behave
❏ how to deal with their limitations
Often with try / fail / learn
methodology.

22. Patch management
Cloud providers offer
up-to-date assets.
But do not upgrade already
provisionned ones!
You have to use immutable
infrastructure management
patterns

23. Integration
Cloud providers offer many
services.
Building a platform means to
integrate 10s of services with
each others.
Cloud architect & devops
guys are deeply needed!

24. Price-driven governance
Usage changes, explosion of your VMs
counter
60% of time spent in operating Cloud
services is to optimize costs – Google
DevFinOps
“Tristar Medical Group Discovers
Solution That Reduced its AWS Costs
by 60% (~$20k per month)”
– May 9, 2018

25. Resiliency

26. Data gravitation / Reversibility
Cloud providers aim to store data.
❏ Weight of data
❏ Data format
❏ Data requesting technos
… lead to make reversibility
difficult.

27. High-end value services / Reversibility
Cloud providers deliver
high-end services that are
❏ quite easy to use
❏ very difficult to migrate from.
For example
❏ cognitive services
❏ authentication services
❏ Spanner
❏ Alexa chatbot

28. Plateau of productivity

29. Focus on value & better TTM
but support platform constraints
More flexibility, more tuning
capacity… but assume plumbing
Functions
ABSTRACT
FOCUSINFRA
Microservices
Monoliths
CaaS
IaaS
FaaS
& PaaS

30. Don’t put all one's eggs in one basket
Create an abstraction layer between your consumers and
cloud providers: let’s hybridate!
❏ Leverage on open-source / standards as much as you can. Notice how much
object storage vendors built up S3 (AWS) compliant APIs?
❏ Make an impact analysis (reversibility, etc.) before making your apps sticky with the
subsequent platform it relies on. (Mind the price upgrade of Google Maps)
❏ There’s no free lunch: possibly assume not to use everything you can?
Platform
AWS AZURE

31. Assume bi-modality

32. Containers & orchestrators

33. People & processes over technology
❏ Infra-as-code, software-defined-xxx: Ops progressively become Devs: you need to
engage on reskilling them!
❏ No longer be a robot, invent robots: it’s not just about hard skills!
❏ While some activities retire, new emerge: low level architecture, IT financing
metrology for instance
❏ Integrate your cloud into a broader devops or continuous delivery transformation
People > Processes > Tools

34. Conclusion
Conclusion

35. Architecture & cloud vendors
❏ App architecture & languages influenced cloud offers:
microservices, app resiliency & scalability contributed to
infrastructure commoditization
❏ Nowadays, the cloud influences you app: object storage,
serverless, cloud native apps
We created junkies, always searching for more abstraction. But
your dealer is not your friend, he as some interests in ($$$)

36. Subtle equilibrists choices
❏ Offload from the non valuable plumbing
❏ … but some infrastructure assets may be
finally part of your differentiators
❏ Get the control back may be valuable:
preserves autonomy, reduce operational
costs at scale...
❏ “Do as I say, not as I do”: refocusing on core-business is the exact opposite of what
cloud vendors does, being themselves fullstack
❏ Be an engineer, not a fashionista

37. (Re) Assess yourself
Time passed, the landscape changed
❏ Technologies are more mature
❏ Consulting/training/documentation... are more
developed
May be the time to get the control back ?

38. Questions ?