This document discusses principles for designing systems with a DevOps mindset. It emphasizes building tools that are highly integrated, abstracted, understandable and promote continuous deployment over "racking boxes" and "putting out fires." The goal is to engineer systems for availability, scalability and resilience rather than manual administration.

1. Designing for DevOps

5. Vehicles for land or air that
carry the dedication to
efficiency, getting along on
little power, that is the
hallmark of soaring!

6. rh um a n
am a t eu
@

7. e nd er s
@ ni cb

9. THIS IS OUR STORY.

10. 51
Billion metrics / Day
547 THOUSAND APPS

11. 2,081,321,280
HTTP REQUESTS

12. 15
SERVERS

13. END-USER OUR CUSTOMER NEW RELIC
Pinger
Collector
Beacon
RPM
WWW

14. Growing Pains

15. DO NOT WANT.

16. racking boxes
is not A
FEATURE.

17. PUTTING OUT
FIRES?
NOT A FEATURE.

18. AVAILABILITY
SCALABILITY

19. AVAILABILITY
SCALABILITY

20. ENGINEER
NOT
ADMINISTER

21. HACKERS over rackers.

22. Generalists

23. Tool Builders

24. DEVELOPERS
Developers
developers

25. BE DELIBERATE.

26. MATURITY

27. MATURITY
UNDERSTANDABILITY

28. MATURITY
UNDERSTANDABILITY
INTEGRATEABLE

29. MATURITY
UNDERSTANDABILITY
INTEGRATEABLE
EASILY ABSTRACTED

30. OPS SHOULD BE
INTERESTING NOT EXCITING.

31. Continuous Deployment

32. Continuous Deployment
Feature flags

33. Continuous Deployment
Feature flags
RESILIENCE

34. OUR TOOLS TELL
US SOMETHING
ABOUT OUR
Culture.

36. Optimize for discovery

37. 30-day free trial at
newrelic.com/30
nic Benders / @nicbenders Chris Kelly / @amateurhuman