So you’ve decided to be “social.” Your awesome new fledgling app will be a new haven for user-generated content, social engagement, and other buzzwords. Unfortunately, the app will need to handle content and graph operations with unbounded size and erratic access patterns. Will users share text? Photos? Music? Video?!
This presentation will cover a hypothetical architecture for a growing site with emphasis on real-world scenarios. Twitter’s FlockDB + Gizzard will handle the massively distributed social graph. Other NoSQL engines (MongoDB, memcache, Redis, maybe even Hadoop) will handle content. Bring your questions and concerns!
Building a team? Looking to join a team? Visit the ChicagoRuby Job Board: jobs.chicagoruby.org.
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?