Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
DevOpsDays Cuba 2016: How the practices of DevOps are evolving from servers to services.
Search
DevOpsDays Cuba
October 20, 2016
Technology
0
56
DevOpsDays Cuba 2016: How the practices of DevOps are evolving from servers to services.
Author: Patrick Debois
Summary:
DevOpsDays Cuba
October 20, 2016
Tweet
Share
More Decks by DevOpsDays Cuba
See All by DevOpsDays Cuba
DevOpsDays Cuba 2017: BigData perspectiva DevOps
devopsdayscuba
0
85
DevOpsDays Cuba 2017: Continuous Delivery with Gitlab Apache Mesos and Marathon
devopsdayscuba
0
580
DevOpsDays Cuba 2017: Workshop - Essential DevOps
devopsdayscuba
0
470
DevOpsDays Cuba 2017: Ignite - Performance test for Web Apps
devopsdayscuba
0
410
DevOpsDays Cuba 2017: El valor de Docker para grupos DevOps
devopsdayscuba
0
430
DevOpsDays Cuba 2017: Starting and Growing Your DevOps Teams
devopsdayscuba
0
300
DevOpsDays Cuba 2017: DEVOPS PITFALLS
devopsdayscuba
0
310
DevOpsDays Cuba 2017: Ignite - Build and install scientific software with EasyBuild in HPC systems
devopsdayscuba
0
330
DevOpsDays Cuba 2017: Ignite - Monitorización más allá de los servicios y sistemas enfoques para Centros de Datos de Nueva Generación
devopsdayscuba
0
350
Other Decks in Technology
See All in Technology
20240717_イケコパ代表Copilot_in_Teams会社でこう使ってます
ponponmikankan
2
430
シフトレフトで挑む セキュリティの生産性向上
sekido
PRO
0
270
技術負債による事業の失敗はなぜ起こるのか / Why do business failures due to technical debt occur?
i35_267
0
190
CEL(Common Expression Language)で書いた条件にマッチしたIAM Policyを見つける / iam-policy-finder
fujiwara3
0
710
DevIO2024_レガシー運用からの脱却 -クラウド活用の実践事例とベストプラクティス-
jun2882
0
210
What if...? 처음부터 다시 LLM 어플리케이션을 개발한다면
huffon
0
1k
初中級者用如何使用backlog -VALE TUDOEDITION-
in0u
0
140
地理情報とAPIのトレンド
nagix
0
160
AWS IAMのアンチパターン/AWSが考える最低権限実現へのアプローチ概略(JAWS-UG朝会#59資料改修20分版)
htan
0
330
コミュニティサービスに「あなたへ」フィードを リリースするまでの試行錯誤
takapy
1
150
LLMアプリケーションの評価の実践と課題 ~PharmaXにおける今後の展望~
pharma_x_tech
2
160
Amazon FSx for NetApp ONTAPのパフォーマンスチューニング要素をまとめてみた #cm_odyssey #devio2024
non97
0
220
Featured
See All Featured
Designing Experiences People Love
moore
136
23k
WebSockets: Embracing the real-time Web
robhawkes
59
7.2k
How To Stay Up To Date on Web Technology
chriscoyier
784
250k
Bash Introduction
62gerente
607
210k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
502
140k
The MySQL Ecosystem @ GitHub 2015
samlambert
248
12k
The Power of CSS Pseudo Elements
geoffreycrofte
64
5.2k
BBQ
matthewcrist
82
9k
Designing with Data
zakiwarfel
96
5k
Thoughts on Productivity
jonyablonski
64
4.1k
The Straight Up "How To Draw Better" Workshop
denniskardys
229
130k
jQuery: Nuts, Bolts and Bling
dougneiner
61
7.4k
Transcript
HOW THE PRACTICES OF DEVOPS ARE EVOLVING from servers to
services @patrickdebois - Small Town Heroes
Things I did (I’m proud of)
OPS DEV http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/ 4 areas of improvement
OPS DEV Area 1: Extend delivery to production http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/
OPS DEV Area 2: Extend operations feedback to project Area
1: Extend delivery to production http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/
OPS DEV Area 2: Extend operations feedback to project Area
1: Extend delivery to production Area 3: Embed Project knowledge into Operations http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/
OPS DEV Area 4: Embed Operations knowledge into Project Area
2: Extend operations feedback to project Area 1: Extend delivery to production Area 3: Embed Project knowledge into Operations http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/
OPS DEV http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/ Technical Loop Business Loop Business Loop
LIVE RESULTS INTERACTION MODERATION STUDIO CONTROL PART OF THE SHOW
Focus on the Business
“Backend” services “IT support” services Our “Office” services “Community” services
“Frontend” services
“Mobile” services SNS/Push Cognito
(almost) NO SERVERS
A bit further down the rabbit hole …
Github service not available
undocumented changes
inconsistent behaviour
different behaviour under load
(almost) NO MAINTENANCE Less Maintenance
increased risk when not available More speed
With increased risk
Functions As a Service (FAAS) aka “serverless”
Case1 Generate “personalised” image Browser -> Pre-signed S3 -> Lambda
-> SQS -> Redis
Case2 Animated gif/movie/meme editor API GW -> Lambda -> Img
magic movie -> s3
None
None
You are an Agent
You make promises to others in the system
Your promises should be verifiable
A promise does not guarantee an outcome
Conditions should be part of your promise
It needs to be clearly documented otherwise it’s not a
promise
It needs to be mutually agreed (not obligation) otherwise it’s
not a promise
You might depend on other agents to keep your promises
Other agents make promises to you
Their promises need to be verifiable clearly documented & mutually
agreed (not obligation)
But you can not make promises on behalf of other
agents (bottom up vs top down)
Promises can be conflicting in a system
but the conflict can only be from internal promises (as
we can not be responsible for others promises)
To keep a promise you should have a choice Push
vs Pull
Single Leaves = SPOF To create choice you need to
eliminate the single leaves (SPOF)
All problems in computer science can be solved by another
level of abstraction
… except for the problem of too many layers of
indirection … David Wheeler (inventor of subroutine)
None
Every promise binding is the basis for relationship (Dunbar)
Agents with a similar goal can be grouped into a
Super Agent
Single Leaves = SPOF You need multiple Super Agents to
have a choice again
Forks v1 v2 v3 v1 v2 v3 To keep promises
agent can introduce different world views (versions)
Slows down A super agent might get slow internal communication
speed is key Opportunity for personalised service providers
Scaling Promises keeping your promise while changing your size (is
hard)
container re-use non-deterministic
limits not clear under stress
services devops
Holy Cow!
“I introduced devops and all I got was a remote
API”
It’s devops Jim but not as we know it
emerging practices
communicate the status of your promise and monitor others
monitor your services and expose your own metrics (API)
expose insights to other agents (API)
show that you care about other agents
expose your logs
be clear on what happens when it fails
backup external data (give an API please)
provide & seek fast feedback on your promise change status
be clear on your dependencies and expect the same of
other services
be proactive to make others keep their promises
give insights on changing promises
blog to communicate your service skill level
talk at conferences to indicate your willingness to share
make it convenient for other agents to use
provide feedback to other agents
show that you listen to those that depend on you
show that your participation by improving the field
show that your engineers are not afraid of talking to
people
let other agents influence your changing promises
“The collaboration between dev & ops is now extended to
external 3rd parties”
“make clear promises to other agents”
“And verify the status of other agents promises”
“To keep your promise to the business”
External Services are the next silo think “Supply Chain”
https://vimeo.com/101735252 DevOpsDays Minneapolis 2014 Jeff Sussna, Promising Digital Service Quality
None
Questions?
[email protected]
www.smalltownheroes.be @patrickdebois