Sessions at Cassandra SF 2011 about Cassandra and Scaling

Monday 11th July 2011

• Cassandra Use Cases at Twitter

  by Chris Goffinet

  Twitter currently runs a couple hundred Cassandra nodes across a half dozen clusters. These span a variety of workloads– from time series to data, to low latency, high throughput key/value. Each workload has led the team to new techniques for operating Cassandra at scale. Chris Goffinet, an engineer at Twitter and Cassandra committer, will be sharing some of the most interesting ones. For those of you interested in Cassandra and operations, this is a must-attend talk.

  • Cassandra
  • Scaling
  • Twitter

  At 10:00am to 11:00am, Monday 11th July

  Coverage slide deck note

• Migration From 100s to 100s of Millions – Messaging to Mobile Devices with Cassandra at Urban Airship

  by Erik Onnen

  • Cassandra
  • Mobile
  • Push Services
  • Scaling
  • Urban Airship

  At 11:00am to 12:00pm, Monday 11th July

  Coverage liveblog note slide deck

• Highly available HTTP request routing and DNS using Cassandra

  by David Strauss

  Cassandra is mostly known for its I/O scalability, but its shared-nothing, highly available foundation is equally useful for applications requiring multi-datacenter distribution and constant uptime. It’s actually quite easy to build and manage HA services by punting the real HA problems to Cassandra’s battle-tested replication and sharding implementation. In this session, we’ll explore Pantheon’s edge routing layer, including:

  • How application servers register their presence in Cassandra with a Twisted Python-based REST API. We’ll test updating routes using using cURL.

  • Using Twisted Python to expose the Cassandra route mappings via DNS. This stack will provide us with a distributed, highly available UDP DNS cluster in about 30 lines of Python code back-ending to Cassandra. We’ll then read routes using the “dig” shell client.

  • Using node.js as an HTTP reverse proxy to look up, cache (in local Redis), and use (with load balancing) routes discovered by reading the “A” records found in DNS. This part tops off the stack and allows us to distribute HTTP requests among application servers registered in Cassandra.

  Since this is a case study, we’ll also consider how Pantheon manages the DNS/Cassandra layer to maintain full availability (read and write) during deployments and data center interlink failures.

  • Cassandra
  • DNS
  • HTTP
  • Node.js
  • Scaling

  At 1:45pm to 2:45pm, Monday 11th July

• Scaling Solr with Cassandra

  by Jake Luciani

  • Cassandra
  • Scaling
  • Solr

  At 3:00pm to 4:00pm, Monday 11th July