Bruce Dembecki
Track: Scaling and High Availability
Date: Wednesday, April 20
Time: 4:50pm - 5:35pm
Location: Ballroom E
TrackBack
Community tools require a two way interaction between the web site and the users. Rather than the "one to many" model common in web publishing over the years, community tools require "many to many" interactivity, where the users provide the content, over and over and over again. This simple difference means that web sites based on community tools have a different set of needs than those of their more traditional counterparts.
In a traditional model the publishing system and the web application are typically separate, and it is common for large scale deployments to publish to one database master and replicate to many slaves, which in turn handle many web app servers. In a community environment, the web application servers ARE the publishing system, and every web app server needs to be able to write and to be aware of changes made by other web app servers. Clearly the one master serving many slaves model of database replication doesnt work in such an environment.
So what are the effects of a truly interactive environment on scale and redundancy? How do you handle failover, replication, caching, tuning, backup, recovery when the writes are almost as voluminous as the reads and the loads are high enough to justify dozens of servers? What are the critical choices, and how do you weigh the importance of redundancy vs. performance vs. scalability?
Come on an interactive journey of discovery with LiveWorlds Bruce Dembecki as he looks at how they have deployed MySQL to serve the needs of their discussion board clients. With over 75 million page views each month, LiveWorld has 60 products deployed in 10 languages for 20 countries, serving clients such as AOL, eBay, HBO, QVC, A&E TV, Warner Brothers, Dove, Mini, and Campbells.
Download presentation file