MediaWiki architecture document/Initial ideas

This page helps structure and plan a potential chapter about MediaWiki in the Architecture of Open Source Applications book.


 * Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.


 * This book's goal is to change that. In it, the authors of twenty-five open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to this book provide unique insights into how they think.

Questions to answer
See MediaWiki architecture document/How and why/questions

Sources to review
Current
 * Manual:Cache
 * Manual:File cache
 * Disk-backed object cache
 * This probably won't be very interesting to anyone but us. ^demon 20:43, 29 September 2011 (UTC)
 * Manual:Code
 * Localisation
 * PHP configuration
 * Requests for comment
 * MediaWiki on Wikipedia
 * Category:MediaWiki components

Historical content
 * w:Special:PrefixIndex/Wikipedia:PHP script
 * w:Wikipedia:MediaWiki (archive)
 * http://meta.wikimedia.org/w/index.php?title=MediaWiki&dir=prev&action=history
 * http://en.wikipedia.org/w/index.php?title=Wikipedia:Software_Phase_III&action=history
 * Release notes
 * m:Cache strategy
 * m:PHP caching and optimization
 * m:Wikimedia cache strategy evolution during 2003
 * One-pass parser
 * m:Category:Category:MediaWiki archives
 * m:Main causes of lag
 * PHPTal
 * User_talk:Brion_VIBBER

(and associated talk pages)