Accept Paradigm Shifts
to
Accelerate Devops
habeeb rahman | @pk.habi | devopsdays India 2013
Apigee
apps
data ( big! )
apis
Devops
is not (just) about
titles ( let’s debate this later )
tools/automation
Devops
is definitely about
people
collaboration
Paradigms
mental maps
lens
Paradigm shift
The significant problems we face cannot be solved
at the same level of thinking we were at
when we created ...
Devops team
will solve your problems ?
may not => without a few paradigm shifts
‘X’ driven development
TDD (Test Driven Development)
BDD (Behaviour Driven Development)
CDD (Customer Driven Development)
...
ODD ( Operations Driven Development )
optimize for your biggest customer
ops/support team
ODD: how to begin?
very early ops engagement ( day 1 )
architect/code with operations in mind
ODD: debuggable?
loglevel = empathy
debuglevel = service level agreement
ODD: silent?
no silent deaths
no silent waiting
ODD: metrics & counters
show the traffic
ODD: app level tracing
show the inner self
ODD: easy to deploy?
rpm vs. tar
config files vs. hardcoding
ODD: dns to db
/etc/hosts vs. dns
new nosql db vs. reliable sql db
experiment but is it production ready yet?
Beyond
Engineering
( just )
the product
‘Engineering’

the infrastructure

tuning - ( i/o | cpu | memory ) bound
scalable?
benchmark
architect for cost saving
‘Engineering’ the tools
same importance as the product development?
full time job ?
hire full time developer ? ( and follo...
Questions?
Upcoming SlideShare
Loading in …5
×

Accept paradigm shifts to Accelerate devops

1,337 views

Published on

Ignite talk given @ Devopsdays India 2013 (16-17 Nov 2013)

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,337
On SlideShare
0
From Embeds
0
Number of Embeds
49
Actions
Shares
0
Downloads
18
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Accept paradigm shifts to Accelerate devops

  1. 1. Accept Paradigm Shifts to Accelerate Devops habeeb rahman | @pk.habi | devopsdays India 2013
  2. 2. Apigee apps data ( big! ) apis
  3. 3. Devops is not (just) about titles ( let’s debate this later ) tools/automation
  4. 4. Devops is definitely about people collaboration
  5. 5. Paradigms mental maps lens
  6. 6. Paradigm shift The significant problems we face cannot be solved at the same level of thinking we were at when we created them. - Albert Einstein
  7. 7. Devops team will solve your problems ? may not => without a few paradigm shifts
  8. 8. ‘X’ driven development TDD (Test Driven Development) BDD (Behaviour Driven Development) CDD (Customer Driven Development) & ?
  9. 9. ODD ( Operations Driven Development ) optimize for your biggest customer ops/support team
  10. 10. ODD: how to begin? very early ops engagement ( day 1 ) architect/code with operations in mind
  11. 11. ODD: debuggable? loglevel = empathy debuglevel = service level agreement
  12. 12. ODD: silent? no silent deaths no silent waiting
  13. 13. ODD: metrics & counters show the traffic
  14. 14. ODD: app level tracing show the inner self
  15. 15. ODD: easy to deploy? rpm vs. tar config files vs. hardcoding
  16. 16. ODD: dns to db /etc/hosts vs. dns new nosql db vs. reliable sql db experiment but is it production ready yet?
  17. 17. Beyond Engineering ( just ) the product
  18. 18. ‘Engineering’ the infrastructure tuning - ( i/o | cpu | memory ) bound scalable? benchmark architect for cost saving
  19. 19. ‘Engineering’ the tools same importance as the product development? full time job ? hire full time developer ? ( and follow ODD )
  20. 20. Questions?

×