the golang effect - how go shaped operations at vividcortex

38

Upload: vividcortex

Post on 05-Jul-2015

345 views

Category:

Technology


1 download

DESCRIPTION

As an early stage startup you need to move fast. It’s important to carefully consider what programming languages you use, tools you adopt, and processes you establish. When we founded VividCortex we evaluated a number of languages and tools to build our services on. We could have picked languages like Java, C++, Scala, or Clojure, but we chose Go (Golang) because it compiles fast, it’s performant, it’s easy to deploy, and easy & fun for developers to learn, in a nutshell it helps us move fast. We also use a “chatops” set of tools and processes to configure, deploy and manipulate our environment: Jenkins, Ansible, and Hubot among others. It’s interesting to see how Go’s characteristics work together with this modern stack, and how the combination has affected our company culture. In this talk we will discuss how we chose our tools, and how the decisions affected our organization as a whole, by inspiring us to adopt tools and processes that are easy to learn, administer, and help us move fast.

TRANSCRIPT

Page 1: The Golang Effect - How Go Shaped Operations At VividCortex
Page 2: The Golang Effect - How Go Shaped Operations At VividCortex
Page 3: The Golang Effect - How Go Shaped Operations At VividCortex
Page 4: The Golang Effect - How Go Shaped Operations At VividCortex
Page 5: The Golang Effect - How Go Shaped Operations At VividCortex
Page 6: The Golang Effect - How Go Shaped Operations At VividCortex
Page 7: The Golang Effect - How Go Shaped Operations At VividCortex
Page 8: The Golang Effect - How Go Shaped Operations At VividCortex
Page 9: The Golang Effect - How Go Shaped Operations At VividCortex
Page 10: The Golang Effect - How Go Shaped Operations At VividCortex
Page 11: The Golang Effect - How Go Shaped Operations At VividCortex
Page 12: The Golang Effect - How Go Shaped Operations At VividCortex
Page 13: The Golang Effect - How Go Shaped Operations At VividCortex
Page 14: The Golang Effect - How Go Shaped Operations At VividCortex
Page 15: The Golang Effect - How Go Shaped Operations At VividCortex
Page 16: The Golang Effect - How Go Shaped Operations At VividCortex
Page 17: The Golang Effect - How Go Shaped Operations At VividCortex
Page 18: The Golang Effect - How Go Shaped Operations At VividCortex
Page 19: The Golang Effect - How Go Shaped Operations At VividCortex
Page 20: The Golang Effect - How Go Shaped Operations At VividCortex
Page 21: The Golang Effect - How Go Shaped Operations At VividCortex
Page 22: The Golang Effect - How Go Shaped Operations At VividCortex
Page 23: The Golang Effect - How Go Shaped Operations At VividCortex
Page 24: The Golang Effect - How Go Shaped Operations At VividCortex
Page 25: The Golang Effect - How Go Shaped Operations At VividCortex
Page 26: The Golang Effect - How Go Shaped Operations At VividCortex
Page 27: The Golang Effect - How Go Shaped Operations At VividCortex
Page 28: The Golang Effect - How Go Shaped Operations At VividCortex
Page 29: The Golang Effect - How Go Shaped Operations At VividCortex
Page 30: The Golang Effect - How Go Shaped Operations At VividCortex
Page 31: The Golang Effect - How Go Shaped Operations At VividCortex
Page 32: The Golang Effect - How Go Shaped Operations At VividCortex
Page 33: The Golang Effect - How Go Shaped Operations At VividCortex
Page 34: The Golang Effect - How Go Shaped Operations At VividCortex
Page 35: The Golang Effect - How Go Shaped Operations At VividCortex
Page 36: The Golang Effect - How Go Shaped Operations At VividCortex
Page 37: The Golang Effect - How Go Shaped Operations At VividCortex
Page 38: The Golang Effect - How Go Shaped Operations At VividCortex