On July 26th, @TwitterEng and @TwitterOSS invite you to an evening of tech talks, frosty beverages and snacks. This will be a developer focused event inside our new headquarters dedicated to some of Runtime Systems open source technologies. Please register as soon as you can since we anticipate hitting our capacity very quickly.

#talks

We plan to present and discuss:

• Distributed tracing with Zipkin (@zipkinproject) by @skr / @thisisfranklin
• Zipkin is a distributed tracing system that helps us gather timing data for all the disparate services at Twitter, and manages collection and lookup of data through a Collector and a Query service. With Zipkin, we can trace a subset of all requests made to the site, and collect detailed data about the path taken through our systems, as well as timings. Then, we can visualize and ultimately pinpoint where and possibly why a response took longer than expected.
• Caching at Twitter with Twemcache (@twemcache) by @manju / @thinkingfish
• Twemcache is Twitter’s forked version of memcached. We’ll briefly review the architecture of the caching system at Twitter and then delve into the details of Twemcache, one of the fundamental building blocks of our caching system. Then, we’ll discuss new features in Twemcache: viz random eviction, lockless stats collection and klogger, and the motivations behind them.
• Twitter and Apache Mesos (@apachemesos) by @benh / @vinodkone
• Apache Mesos is a platform that provides efficient resource isolation and sharing for distributed applications and frameworks. You can use Mesos to run Hadoop, MPI, Spark, Storm and others using the same cluster. Mesos is also helpful in building novel distributed applications and frameworks. In this talk I'll discuss the architecture and motivation behind Mesos and how it is currently being used at Twitter and elsewhere.

Be sure to start tweeting with the event hashtag #rtsoss and help us get the word out!