When a project leaves the nest: Community driven development and OpenZipkin

Slide 1

Slide 1 text

When a project leaves the nest Community driven development and OpenZipkin @adrianfcole

Slide 2

Slide 2 text

@adrianfcole • spring cloud at pivotal • focus on distributed tracing • helped open zipkin

Slide 3

Slide 3 text

zipkin • so.. like Chrome DevTool’s network panel • .. except it is for your whole architecture https://github.com/openzipkin

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

It started with community focus

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Answers to the problem evolved

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

commit 92c941890c2009a401b777093342dc4f28955640 Author: Johan Oskarsson Date: Tue Nov 15 10:09:47 2011 -0800 [split] Enable B3 tracing for TFE. Filter out finagle-http headers from incoming requests BigBrotherBird is silently born

Slide 10

Slide 10 text

Zipkin is less silently born commit 2b7acead044e71c744f39804abe564383eb5f846 Author: Johan Oskarsson Date: Wed Jun 6 11:28:34 2012 -0700 Initial commit

Slide 11

Slide 11 text

And it all seemed to be working!

Slide 12

Slide 12 text

And engineering at Twitter continued

Slide 13

Slide 13 text

And engineering outside Twitter continued

Slide 14

Slide 14 text

Turns out, internal and external communities behave differently

Slide 15

Slide 15 text

zipkin says “we are a community”

Slide 16

Slide 16 text

So what happened? • Zipkin development at Twitter was in short bursts, centered on other work • Many experienced Zipkin engineers don’t work at Twitter (nor live in the Bay Area) • Platform diversity is a reality for many • Having the same goals was our opportunity

Slide 17

Slide 17 text

(open)zipkin left the nest

Slide 18

Slide 18 text

and, I did too.. this deck is that blog.. yeah..

Slide 19

Slide 19 text

we have small whales • Not everyone came back • Some change needed to be reversed • Stabilizing one’s today while progressing another’s tomorrow is a difﬁcult balance

Slide 20

Slide 20 text

yet, the community has never been so strong • Change in zipkin comes from more people across most timezones, for various systems • The zipkin community routinely collaborates with others like OpenTracing • We are learning, but make choices as we go

Slide 21

Slide 21 text

Thank you! cloud.spring.io pivotal.io gitter openzipkin/zipkin @adrianfcole So.. it’s all worth it