Archives (2008 - 2023)

The Designing Social Interfaces patterns wiki is a companion site to the book that Christian Crumlish and Erin Malone are currently writing for O'Reilly Media.

We decided to share the patterns as we write the patterns and the book to get community feedback. We think that hearing a variety of opinions about these topics will make the material stronger and more representative of what's happening in social interfaces. As we complete sections of the book, we will be adding the patterns.

If you choose to contribute, we ask that you don't delete sections out right, but rather add your information with attribution. We want to incorporate contributions into the final book material and would like to know who contributed what. Every page has a discussion tab for conversations about the topic.

We look forward to talking with you

The Tungsten Replicator implements open source database-neutral master/slave replication. Master/slave replication is a highly flexible technology that can solve a wide variety of problems including the following:

* Availability - Failing over to a slave database if your master database dies
* Performance Scaling - Spreading reads across many copies of data
* Cross-Site Clustering - Maintaining active database replicas across WANs 
* Change Data Capture - Extracting changes to load data warehouses or update other systems
* Zero Downtime Upgrade - Performing upgrades on a slave server which then becomes the master

In summary, if your organization plans to use SharePoint 2007 primarily as a CMS, evaluate it as you would any other CMS. I think we can all agree that pretty much all content management systems are crippled, but at least you’ll be able to customize the entire experience — interaction, design, markup, and so forth.

If using it as a collaboration tool, treat it as licensed software with minimal branding customization. Or better yet, avoid it like the plague and convince your organization to go with Clearspace or even Basecamp.