GoSF: Problematic Dependencies, Origin Cache for Images, OpenTracing and Go

Agenda

6:00 Networking | Food | Drink

6:30 A word from the sponors

6:40 Speakers

• Talk 1: Managing Problematic Dependencies: A Path to Sanity by Greg Poirier

About a year ago, Opsee began a project of retooling all of its internal communication around gRPC and protobuf v3. We wanted a shared models collection that we could use to easily facilitate passing entities between services, and gRPC+protobuf seemed to be a great fit. It worked well for us—until gRPC introduced the first backward-incompatible change to its API—until we started generating more code in more places using different tools—etc. etc. until we cornered ourselves in a nightmarish hellscape of dependency mismanagement.
In this talk, we’ll explore how we got ourselves into this predicament, and how we’re planning to dig ourselves out. We’ll look at our proposed solutions, and evaluate their pros and cons.

BIO:

Greg is the CTO and founding engineer at Opsee where he’s building the monitoring product he always wanted. When not writing Go or giving talks, Greg is usually playing piano or singing.

• Talk 2: Building Scalable Slack bots with Go

Relax: a Slack bot framework that helps you build slack bots that scale to 1000s of teams

BIO:

Arun is the founder of Ze Robot Labs and has been working on Slack bots for the last year. He has a couple of products: Nestorhttps://www.asknestor.me (https://www.asknestor.me/) which is a programmable Slack bot and Botmetrics https://getbotmetrics (https://getbotmetrics.com/).com (https://getbotmetrics.com/) which is an analytics platform for intelligent agents.

• Talk 3: Turnkey Distributed Tracing: OpenTracing and Go

This talk describes why distributed tracing is important, why its instrumentation presents uncommon standardization problems, the way that OpenTracing addresses these problems, and how Go is such a convenient language for OpenTracing integrations. It's been 12 years since Google started using Dapper internally. Zipkin was open-sourced over 4 years ago. This stuff is not new! Yet if you operate a complex services architecture, deploying a distributed tracing system today requires person-years of engineer effort, monkey-patched communication packages, and countless inconsistencies across platforms. If distributed tracing is so valuable, why doesn't everyone do it already? Because tracing instrumentation has been broken until now.That brings us to the OpenTracing project. OpenTracing is a new, open distributed tracing standard for applications and OSS packages. I will describe how OpenTracing integrates with application code and OSS libraries, how it interoperates with Zipkin, Appdash, LightStep, and other tracing backends, and where the project is headed. We will end with a deep dive of the Go OpenTracing library and show a few demos.

BIO:

Ben Sigelman is the CoFounder and CEO of LightStep where he's building reliability management for modern systems. As an expert in distributed tracing, he is a leading proponent of the OpenTracing standard. In the past he built Dapper, Google's production distributed systems tracing infrastructure.

8:30 End

THANK YOU TO OUR SPONSORS:

http://photos2.meetupstatic.com/photos/event/7/2/2/a/600_451109226.jpeg

See the availability and performance of your sites, APIs and internal services in one place with Opsee (https://opsee.com/). Get global coverage of your public sites and APIs - checks run from all 6 of our locations around the world, every 30 seconds, with nothing to install. Get complete AWS coverage too when you add our EC2 instance to your environment. Check your services and CloudWatch metrics with no agents to run.

http://photos3.meetupstatic.com/photos/event/7/2/3/1/600_451109233.jpeg

LightStep is reliability management for modern systems. Our product enables developers and devops to trace individual requests through complex systems all the way from mobile clients to microservices with incredibly high fidelity using distributed tracing.