Designing for-devops
•
0 likes•300 views
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.
Report
Share
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.
- 20. ENGINEER NOT ADMINISTER
- 22. Generalists
- 23. Tool Builders
- 25. BE DELIBERATE.
- 26. MATURITY
- 30. OPS SHOULD BE INTERESTING NOT EXCITING.
- 34. OUR TOOLS TELL US SOMETHING ABOUT OUR Culture.
- 37. 30-day free trial at newrelic.com/30 nic Benders / @nicbenders Chris Kelly / @amateurhuman