DevOpsDays Raleigh 2016
At Kickstarter, the Ops Engineering team recently deployed Elasticsearch/Logstash/Kibana to centralize application logs. I’ll use our implementation of the ELK stack as a case-study to examine our process for choosing tools, particularly:
when to build vs. buy
what features we need in the initial version, and what can wait until later
when to invest effort in an elegant solution, or when to get by with a hack.
This talk will discuss what factors influenced our decisions (context); and what future changes could lead to a different choice (contingency).
By capturing the context and contingency of our choices, we can more easily adapt to changes in our organization and the tech community.
I’ll show how our implementation decisions impacted the processes and behaviors of our team; which in turn influenced and reflected our organization’s culture.