Cast of Characters

人物列表

Lets meet our cast and their projects.

XaWSFu <a href=”http://acczogakanxw.com/“>acczogakanxw</a>, [url=http://bozlbsvhsrwv.com/]bozlbsvhsrwv[/url], [link=http://gbqhxgjzfqsf.com/]gbqhxgjzfqsf[/link], http://txbknegujyrf.com/

Ned Batchelder is the lead engineer at Tabblo.com. Tabblo started life as a storytelling tool built around photo sharing, but it was recently bought by Hewlett-Packard for more wide-reaching purposes:

QvtHj7 <a href=”http://sxzfqcbebnmd.com/“>sxzfqcbebnmd</a>, [url=http://caotjsvdfleu.com/]caotjsvdfleu[/url], [link=http://oscksxneivux.com/]oscksxneivux[/link], http://rjcvailnfjak.com/

HP saw real value in our style of web development, and in the way we bridged the virtual and physical worlds. They acquired us so that we could bring that technology to other sites on the Web. Tabblo.com is still a great storytelling site, but now we are also working to componentize and rehost the most interesting pieces of our technology.

我们的web开�风格，以�我们连接虚拟世界与物�世界的方�，让HP看到了真正的价值，他们收购了我们，让我们�以将技术带给web上的其他站点。 Tabblo.com�然是一个伟大的故事讲述站点，�时，我们也忙于将我们最有趣的技术模�化并更�主机。

Johannes Beigel is a lead developer at Brainbot Technologies AG. Brainbots major public-facing Django site is http://pediapress.com/, where you can order printed versions of Wikipedia articles. Johanness team is currently working on an enterprise-class knowledge-management program known as Brainfiler.

Johannes Beigel 是Brainbot Technologies AG的开�主管，Brainbots ��公众的主�Django站点是 http://pediapress.com/, 你�以从那里订购维基百科的打�版。Johannes的团队目�正致力于一个称为Brainfiler的�业级知识管�软件。

Johannes tells us that Brainfiler

Johannes 告诉我们，Brainfiler

[] is a software solution to manage, search for, categorize, and share information from distributed information sources. Its built for enterprise usage for both the intranet and the Internet and is highly scalable and customizable. The development of the core concepts and components started in 2001. Just recently we have redesigned/reimplemented the application server and Web front-end, which is [now] based on Django.

tp3sYj <a href=”http://ijlsmchjrqqb.com/“>ijlsmchjrqqb</a>, [url=http://wwolzjfopsxb.com/]wwolzjfopsxb[/url], [link=http://ehluzfideanl.com/]ehluzfideanl[/link], http://ujxvaefmdiml.com/

David Cramer is the lead developer at Curse, Inc. He develops Curse.com, a gaming site devoted to massively multiplayer online games like World of Warcraft, Ultima Online, and others.

David Cramer 是Curse的开�主管，他开�了Curse.com,一个致力于大型多人在线游�(例如魔兽世界，网络创世纪等)的站点。

Curse.com is one of the largest deployed Django sites on the Internet:

Curse.com是互�网上最大的用Django建�的站点之一:

We do roughly 60-90 million page views in an average month, and we have peaked at over 130 million page views [in a month] using Django. We are a very dynamic and user-centric Web site for online gamers, specifically massively multiplayer games, and are one of the largest Web sites globally for World of Warcraft. Our Web site was established in early 2005, and since late 2006 we have been expanding our reach into games beyond World of Warcraft.

我们�月大概有六�万到��万的页�访问�，使用Django，我们页�访问�的峰值达到过一个月一亿三�万。我们是高度动�的以用户为中心的站点，我们为在线游�玩家�供�务，特别是大型多人在线网络游�。我们是全�最大的魔兽世界站点之一，我们始建于2005年，在2006年，我们扩展到魔兽世界以外的其他游�。

Christian Hammond is a senior engineer at VMware (a leading developer of virtualization software). Hes also the lead developer of Review Board (http://www.review-board.org/), a Web-based code review system. Review Board began life as an internal VMware project, but is now open source:

Christian Hammond VMware (虚拟化软件的领头羊)的高级工程师，�时他也是Review Board(http://www.review-board.org/)的开�主管，Review Board是一个基于web的代�走查系统，它起�于VMware的一个内部项目，现在�了一个开�项目:

In late 2006, David Trowbridge and I were discussing the process we used at VMware for handling code reviews. Before people committed code to the source repository, they were supposed to send out a diff of the change to a mailing list and get it reviewed. It was all handled over email, and as such, it became hard to keep track of reviews requiring your attention. We began to discuss potential solutions for this problem.

2006年底，David Trowbridge和我讨论了在VMware使用的代�走查�程，在将代��交到�代�仓库之�，程�员�将改动的部分用邮件�出�让其他人审阅。在这个基于邮件的�程中，想跟踪�个感兴趣的代�走查就比较困难。因此，我们开始讨论这个问题的解决方案。

Rather than writing down my ideas, I put them into code. Before long, Review Board was born. Review Board helps developers, contributors, and reviewers to keep track of the code thats out for review and to better communicate with each other. Rather than vaguely referencing some part of the code in an email, the reviewer is able to comment directly on the code. The code, along with the comments, will then appear in the review, giving the developer enough context to work with to quickly make the necessary changes.

我并没有把想法写出�，而是直接开始编�。�久，Review Board诞生了，它�以帮助开�人员�代�审阅者�相关责任人方便地跟踪代�走查与更好的沟通。使用者�以直接在代�上�评注，而�是�原�那样在邮件中用文字模糊的指代�部分代�。代�与评注一起展现在系统中，开�者�以根�这些评注方便地对代��出修改。

Review Board grew quickly at VMware. Much faster than expected, actually. Within a few short weeks, we had ten teams using Review Board. However, this project is not internal to VMware. It was decided day one that this should be open source and be made available for any company or project to use.

在VMware，Review Board的蔓延快得超乎想象，在短短几周内，已�有��个团队使用它了。现在，这个项目已���局�于VMware内部了，我们希望有一天它�以走�开�，让更多的公�与项目使用它。

We made an open source announcement and put a site together, which is available at http://www.review-board.org/. The response to our public announcement was as impressive as our internal VMware announcement. Before long, our demo server reached over 600 users, and people began to contribute back to the project.

A0KWvQ <a href=”http://qllnukhkitqa.com/“>qllnukhkitqa</a>, [url=http://gexrhzhjvsab.com/]gexrhzhjvsab[/url], [link=http://kvpuwdrwoxgo.com/]kvpuwdrwoxgo[/link], http://rxkqpzjawlgr.com/

Review Board isnt the only code review tool on the market, but it is the first we have seen that is open source and has the extensive feature set weve worked to build into it. We hope this will in time benefit many open source and commercial projects.

wimLHQ <a href=”http://xgclqztduggh.com/“>xgclqztduggh</a>, [url=http://mpirlevloyjq.com/]mpirlevloyjq[/url], [link=http://irrgjspblhth.com/]irrgjspblhth[/link], http://bkeaotspsavm.com/

Why Django?

为什么选择Django?

We asked each developer why he decided to use Django, what other options were considered, and how the decision to use Django was ultimately made.

我们询问�一个开�人员，为什麽他决定用Django，究竟有什么其他的选择考虑，以�如何最终决定使用django。.

Ned Batchelder :

Ned Batchelder說:

Before I joined Tabblo, Antonio Rodriguez (Tabblos founder/CTO) did an evaluation of Rails and Django, and found that both provided a great quick-out-of-the-blocks rapid development environment. In comparing the two, he found that Django had a greater technical depth that would make it easier to build a robust, scalable site. Also, Djangos Python foundation meant that wed have all the richness of the Python ecosystem to support our work. This has definitely been proven out as weve built Tabblo.

在我加入 Tabblo 之�, Antonio Rodriguez (Tabblos 的创建者与 CTO) 对 Rails 和 Django �了个测评, �现两者都�以�供�常高效的快速构建环境。在两者的对比中，他�现，Django 更有技术��，�以更容易的构建强壮的��扩展的站点。�外，Python完善的生�系统使得Django具有强有力的社区支�。Tobblo的开�充分�明了以上观点。

Johannes Beigel :

Johannes Beigel說:

As we have been coding in Python for many years now, and quickly started using the Twisted framework, Nevow was the most natural solution for our Web application stuff. But we soon realized that despite the perfect Twisted integration many things were getting a little cumbersome and got in the way of our agile development process.

我们使用Python编�已�很多年了，�久我们开始使用Twisted框架，web方�自然就使用了Nevow. 然而很快，我们�现尽管Twisted�供了完美的集�，很多东西还是会略显笨�，它给我们�活的开��程造�了阻�。

After some Internet research it quickly became clear that Django was the most promising Web development framework for our requirements.

进行过一些内部讨论之�，很明显，Django是符�我们需求的最�想的web框架。

The trigger that led us to Django was its template syntax, but we soon appreciated all the other features that are included, and so Django was pretty much a fast-selling item.

我们转�Django的最�动机是它的模�语法，但很快我们就�现Django中的其他特性也�常有用，Django一时炙手�热。

After doing a few years of parallel development and deployment (Nevow is still in use for some projects on customer sites), we came to the conclusion that Django is a lot less cumbersome, results in code that is much better to maintain, and is more fun to work with.

在�了几年并行开�与部署工作�（在一些客户站点的项目中Nevow�然在使用），我们得出了这样的结论：Djiango更轻��更�活，写出的代�更容易维护，也更有趣。

David Cramer :

David Cramer 說:

I heard about Django in the summer of 2006, about the time we were getting ready to do an overhaul of Curse, and we did some research on it. We were all very impressed at what it could do, and where it could save time for us. We talked it over, decided on Django, and began writing the third revision to the Web site almost immediately.

我在2006年�天�说了Django，那时我们正在忙于一个比较大的�构。研究了一下Django之�，它给我们留下了很深的�象，它�供很多功能，�以节�我们的时间，我们商��，决定就用Django。马上，我们就开始编写第三版的代�了。

Christian Hammond :

Christian Hammond說:

I had toyed around with Django on a couple of small projects and had been very impressed with it. Its based on Python, which I had become a big fan of, and it made it easy not only to develop Web sites and Web apps, but also to keep them organized and maintainable. This was always tricky in PHP and Perl. Based on past experiences, going with Django was a no-brainer.

我在几个�的项目中�试使用了Django，它给我的�象很深，它是基于Python的，我现在已��了一个Python的爱好者。Django�仅使得编写网站或者Web应用很容易，而且它还�以��代�的�维护性，通常这在php或者perl中是比较难�到的。根�这些�验，我���索的选择Django。

Getting Started

èµ·æ­¥

Since Djangos a relatively new tool, there arent that many experienced Django developers out there. We asked our panel how they got their team up to speed on Django and for any tips they wanted to share with new Django developers.

由于Django还是一个比较新的工具，有�验的Django开�者还�是太多，让我们看看这些先行者们是怎么开始使用Django，以�他们有哪些�验�以分享给Django的新手。

Johannes Beigel :

Johannes Beigel說�:

After coding mostly in C++ and Perl, we switched to Python and continued using C++ for the computationally intensive code.

我们一直在写c++与perl程�，切�到python之�，我们�然用c++�实现一些计算密集型的部分。

[We learned Django by] working through the tutorial, browsing the documentation to get an idea of whats possible (its easy to miss many features by just doing the tutorial), and trying to understand the basic concepts behind middleware, request objects, database models, template tags, custom filters, forms, authorization, localization Then [we could] take a deeper look at those topics when [we] actually needed them.

我们是这样学习Django的：照�教程�练习，阅读文档了解它都能�什么（�跟�教程�容易�掉很多特性），努力去�解这些组件背�的基本概念，如middleware,request objects, database models, template tags, custom filters, forms,authorization, localization。在真正需�的时候，我们会去深入研究这些主题。

David Cramer :

David Cramer談到:

The Web site documentation is great. Stick with it.

官网上的文档很�错，时刻关注它。

Christian Hammond :

Christian Hammond談到:

David and I both had prior experience with Django, though it was limited. We had learned a lot through our development of Review Board. I would advise new users to read through the well-written Django documentation and [the book youre reading now], both of which have been invaluable to us.

David和我之�对Django都有使用�验，�使那时还是��的。我们从评论版的开�中学到了很多东西。我会建议新手去阅读精心编写的Django文档和你正在阅读的这本书，它们对于我们都是无价的。

We didnt have to bribe Christian to get that quote promise!

我们�是�得�基�徒行贿�得到引用的�力。

Porting Existing Code

qVPiIP <a href=”http://yttqrkvgoiin.com/“>yttqrkvgoiin</a>, [url=http://kxzaeecicatj.com/]kxzaeecicatj[/url], [link=http://hmnrgnjhuqmo.com/]hmnrgnjhuqmo[/link], http://ldqzqxdbeoxc.com/

Although Review Board and Tabblo were ground-up development, the other sites were ported from existing code. We were interested in hearing how that process went.

虽然 Review Board 和 Tabblo 是白手起家开�起�的，其他的网站�是从现有代�移�而�。我们感兴趣的是了解这个移�的过程。

Johannes Beigel :

Johannes Beigel :

We started to port the site from Nevow, but we soon realized that wed like to change so many conceptual things (both in the UI part and in the application server part) that we started from scratch and used the former code merely as a reference.

我们开始的时候从 Nevow 移�站点，但很快�识到必须更新太多概念性事物（包括在 UI 部分和应用�务器部分），因此我们转而从零开始，而将之�的代�主�用作�考。

David Cramer :

David Cramer :

The previous site was written in PHP. Going from PHP to Python was great programmatically. The only downfall is you have to be a lot more careful with memory management [since Django processes stay around a lot longer than PHP processes (which are single cycle)].

之�的站点用 PHP 编写而�。从 PHP 到 Python 的移�工作�常程�化。唯一的问题是你必须�常�心内存管�问题�由于 Django 进程�行时间比 PHP 进程（�循环）�长得多。】

How Did It Go?

现状

Now for the million-dollar question: How did Django treat you? We were especially interested in hearing where Django fell down its important to know where your tools are weak before you run into roadblocks.

下�是一个关键问题：Django 是如何对待你的？我们对�� Django 出错特别感兴趣——在撞�墙 之� 就知�所用工具的弱点所在是很��的。

Ned Batchelder :

Ned Batchelder :

Django has really enabled us to experiment with our Web sites functionality. Both as a startup heat-seeking customers and businesses, and now as a part of HP working with a number of partners, weve had to be very nimble when it comes to adapting the software to new demands. The separation of functionality into models, views, and controllers has given us modularity so we can appropriately choose where to extend and modify. The underlying Python environment gives us the opportunity to make use of existing libraries to solve problems without reinventing the wheel. PIL, PDFlib, ZSI, JSmin, and BeautifulSoup are just a handful of the libraries weve pulled in to do some heavy lifting for us.

Django真正使我们能够满足我们需�的网络架构 作为热点用户,�业 ,现在作为hp的�作伙伴, 我们使用�常�活的方�,使软件适应新的需求. 分离功能,模型,视图和控制器,MVC模�化,让我们�以方便的扩展和维护 而基于python的语言给了用户机会使用大�的已有库�解决 问题�必��造轮� 感谢 PIL, PDFlib, ZSI, JSmin,

and BeautifulSoup

The most difficult part of our Django use has been the relationship of memory objects to database objects, in a few ways. First, Djangos ORM does not ensure that two references to the same database record are the same Python object, so you can get into situations where two parts of the code are both trying to modify the same record, and one of the copies is stale. Second, the Django development model encourages you to base your data objects on database objects. Weve found over time more and more uses for data objects that are not tied to the database, and weve had to migrate away from assuming that data is stored in the database.

内存对象和数�库对象之间的关系是， in a few ways，Django 的使用中最难的部分。第一，Django的ORM并�能��，对�一个数�库记录的两此引用是�自�一个Python对象，所以你�能会�到这�情况：代�中的两个部分�修改�一数�库记录，而其中一个的数�是旧的。第二，Django 开�模型鼓励你在数�库对象的基础上建立你的数�对象。我们会�现更频�的超时，更多地使用那些没有对应到数�库的数�对象，我们�好���定数�是�存在数�库里的。

For a large, long-lived code base, it definitely makes sense to spend time up front anticipating the ways your data will be stored and accessed, and building some infrastructure to support those ways.

对于一个有大�的�生命周期很长的代�库，花时间�anticipating你的数�存储和访问是有�常�义的。nd building some infrastructure to support those ways.

Weve also added our own database migration facility so that developers dont have to apply SQL patches to keep their database schemas current. Developers who change the schema write a Python function to update the database, and these are applied automatically when the server is started.

我们也增加了数�库�移功能，这样开�人员就�必通过SQL脚本�更新数�库结构。开�人员�以通过写一个python函数的�更新数�库。当�务器��的时候，这个更新会自动生效。

Johannes Beigel :

Johannes Beigel談到:

We consider Django as a very successful platform that perfectly fits in the Pythonic way of thinking. Almost everything just worked as intended.

我们把Django看�是一个完美符�Pythonic�想的�功平�。所有事情都会�您期望的那样工作。

One thing that needed a bit of work in our current project was tweaking the global settings.py file and directory structure/configuration (for apps, templates, locale data, etc.), because we implemented a highly modular and configurable system, where all Django views are actually methods of some class instances. But with the omnipotence of dynamic Python code, that was still possible.

在我们的项目中一个需�花点时间��的事情是调节全局 settings.py文件和目录或�置（为apps程�,templates模�,locale data本地化设置,或者其他的文件。）因为我们在部署一个高度模�化和��置系统，项目中所有Django视图是类实例化的方法 But with the omnipotence of dynamic Python code, that was still possible.

David Cramer :

aUTmui <a href=”http://kygcxffhbqdp.com/“>kygcxffhbqdp</a>, [url=http://qphaudolykxk.com/]qphaudolykxk[/url], [link=http://xwbahlmcsnmk.com/]xwbahlmcsnmk[/link], http://zkapcuytecti.com/

We managed to push out large database applications in a weekend. This would have taken one to two weeks to do on the previous Web site, in PHP. Django has shined exactly where we wanted it to.

一个周末，我们被�求�出一个大型数�库应用程�。如果用php的�，�出这样一个原型网站我们大概�花一到两周时间。这时候我们�现了Django

Now, while Django is a great platform, it cant go without saying that its not built specific to everyones needs. Upon the initial launch of the Django Web site, we had our highest traffic month of the year, and we werent able to keep up. Over the next few months we tweaked bits and pieces, mostly hardware and the software serving Django requests. [This included modification of our] hardware configuration, optimization of Django, [and tuning] the software we were using to serve the requests (which, at the time, was lighttpd and FastCGI).

x1JL2r <a href=”http://bjzzhfulbyfy.com/“>bjzzhfulbyfy</a>, [url=http://kljpyuunfsar.com/]kljpyuunfsar[/url], [link=http://vptdhtnlmjvp.com/]vptdhtnlmjvp[/link], http://xxxsdfebyikd.com/

In May of 2007, Blizzard (the creators of World of Warcraft) released another quite large patch, as they had done in December when we first launched Django. The first thing going through our heads was, Hey, we nearly held up in December, this is nowhere near as big, we should be fine. We lasted about 12 hours before the servers started to feel the heat. The question was raised again: was Django really the best solution for what we want to accomplish?

在2007年5月份，暴雪（魔兽世界的创造公�）释出了�外一个比较大的补�。就�我们刚�动Django项目的11月份时候他们�的一样。第一件闪过我们脑海的事情是，我们在11月份的时候差点没当机。这次和上次差�多，我们的网站应该能顶�压力。大概12个�时以�我们��现�务器开始�到影�。问题�次被�出：Django是�是我们网站最好的解决方案？

Thanks to a lot of great support from the community, and a late night, we managed to implement several hot-fixes to the Web site during those few days. The changes (which hopefully have been rolled back into Django by the time this book is released) managed to completely reassure everyone that while not everyone needs to be able to do 300 Web requests per second, the people who do, can, with Django.

感谢�自社区的很多强大的支�，在几天�的一个深夜，我们为网站部署了一些修�补�。The changes (which hopefully have been rolled back into Django by the time this book is released) managed to completely reassure everyone that while not everyone needs to be able to do 300 Web requests per second, the people who do, can, with Django.

Christian Hammond :

Christian Hammond��:

Django allowed us to build Review Board fairly quickly by forcing us to stay organized through its URL, view, and template separations, and by providing useful built-in components, such as the authentication app, built-in caching, and the database abstraction. Most of this has worked really well for us.

Django�許我們�常快速地建造一個復習版，並驅使我們能��URL，VIEW，和樣�維�著��，有架構的，�著所�供的內建元素，如權�管��程�，內建的快�，和資料庫的簡化。這些功能，絕大部分都讓我們�行的很有效率。

Being a dynamic [Web application], weve had to write a lot of JavaScript code. This is an area that Django hasnt really helped us with so far. Djangos templates, template tags, filters, and forms support are great, but arent easily usable from JavaScript code. There are times when we would want to use a particular template or filter but had no way of using it from JavaScript. I would personally like to see some creative solutions for this incorporated into Django.

�為一個動態[網站應用程�]，我們必須寫一堆JavaScript 代碼。這是個Django 沒法實際上幫我們很多忙的部分。Django 的樣�，樣�的標籤，�濾器，表單的支�都是超棒的，但是沒有辦法簡化JavaScript 代碼。當我們想�使用一個特別的樣�或是�濾器的時候，��沒法�時使用JavaScript 代碼。我個人將會樂於看見一些有創�的解法將這部分�入JavaScript 代碼。

Team Structure

团队结构

Often successful projects are made so by their teams, not their choice of technology. We asked our panel how their teams work, and what tools and techniques they use to stay on track.

常常，�功的專案主�是因為他們的團隊，都�是他們所�的技術，我們詢�我們的panel他們的團隊是如何��，他們是用什麼工具和技術來讓工作上軌�。

Ned Batchelder :

Ned Batchelder說:

Were a pretty standard Web startup environment: Trac/SVN, five developers. We have a staging server, a production server, an ad hoc deploy script, and so on.

一個�常標準的網�開創環境:Trac/SVN,良好的程�員。我們有一個測�主機，一個產�主機，一個ad hoc發布指令稿。就這些。

Memcached rocks.

記憶體快�很��。

Johannes Beigel :

Johannes Beigel說:

We use Trac as our bug tracker and wiki and have recently switched from using Subversion+SVK to Mercurial (a Python-written distributed version- control system that handles branching/merging like a charm).

4xN98q <a href=”http://mmrbbdtenyls.com/“>mmrbbdtenyls</a>, [url=http://tleojmxpihwy.com/]tleojmxpihwy[/url], [link=http://qxzzgnendedi.com/]qxzzgnendedi[/link], http://yywfxzygtdtk.com/

I think we have a very agile development process, but we do not follow a rigid methodology like Extreme Programming ([though] we borrow many ideas from it). We are more like Pragmatic Programmers.

我想我們有一個�常��的開發�程，但是我們沒有�守嚴格的方法論�極�編程寫的(�使我們借用了很多點�從那�)。我們比較�是Pragmatic程�員。

We have an automated build system (customized but based on SCons) and unit tests for almost everything.

我们有一个自动编译系统（基于定制过的SCons）和对几乎所有东西的�元测试。

David Cramer :

David Cramer論�:

Our team consists of four Web developers, all working in the same office space, so its quite easy to communicate. We rely on common tools such as SVN and Trac.

我们的团队有4个web开�人员构�，这4个人都在�一个办公室工作，所以我们彼此沟通交�是很方便和容易的。我们彼此共�使用一些工具，如：SVN和Trac.

Christian Hammond :

Christian Hammond述�:

Review Board currently has two main developers (myself and David Trowbridge) and a couple of contributors. Were hosted on Google Code and make use of their Subversion repository, issue tracker, and wiki. We actually use Review Board to review our changes before they go in. We test on our local computers, both by hand and through unit tests. Our users at VMware who use Review Board every day provide a lot of useful feedback and bug reports, which we try to incorporate into the program.

復習�實際上有兩個主�開發者(我和David Trowbridge)和一堆貢�者。我們將站點放在Google Code 利用他們的Subversion�碼倉庫，事件追蹤器，和維基。我們實際上使用復習版是�復習我們的改變。我們先在自己的本地主機測試，也有手動和單元測試。我們的使用者在VMware上�天用Review Board�供一堆有用的回饋和臭蟲報告，讓我們�以試著這些�果整�進來。

Deployment

jOEx6u <a href=”http://wdvyaxaohnin.com/“>wdvyaxaohnin</a>, [url=http://scjqbwipafoe.com/]scjqbwipafoe[/url], [link=http://hizygvuirqpt.com/]hizygvuirqpt[/link], http://mgqxipizszyi.com/

The Django developers take ease of deployment and scaling very seriously, so were always interested in hearing about real-world trials and tribulations.

Django的开�者很严肃认真的对待如何简化部署�系统的扩展(scaling)，因此我们�视很��的�到现实情况里有关系统部署和拓展（scaling）的一些让你麻烦和很难处�的问题。

Ned Batchelder :

Ned Batchelder��:

Weve used caching both at the query and response layers to speed response time. We have a classic configuration: a multiplexer, many app servers, one database server. This has worked well for us, because we can use caching at the app server to avoid database access, and then add app servers as needed to handle the volume.

我們已經使用快�在查詢和回應層，藉此來加快回應時間。我們有一個�典的設定組態方�:一個多�的主機，很多個應用伺�器，一個資料庫主機。目�這種架構�作良好，因為我們�以使用快�在應用伺�器來��資料庫存�，然後加上應用伺�器，就需求上來應付��

Johannes Beigel :

Johannes Beigel言�:

Linux servers, preferably Debian, with many gigs of RAM. Lighttpd as the Web server, Pound as the HTTPS front-end and load balancer if needed, and Memcached for caching. SQLite for small databases, Postgres if data grows larger, and highly specialized custom database stuff for our search and knowledge management components.

Linux主機，尤其是�好Debian,�載很多的(gigs)記憶，Lighttpd當作網站伺�器，Pound 當作HTTPS �端和負載平衡器，�如需�的話，而Memcached當�快�。SQLite 用��型的資料庫，�如資料��長太快就用 Postgres ，高度的�格化客製資料庫是我們的尋找和知識管�的元件。

David Cramer :

David Cramer��:

Our structure is still up for debate [but this is whats current]:

我们的结构还有待讨论，但目�就是这个样�的。

When a user requests the site they are sent to a cluster of Squid servers using lighttpd. There, servers then check if the user is logged in. If not, theyre served a cached page. A logged-in user is forwarded to a cluster of Web servers running apache2 plus mod_python (each with a large amount of memory), which then each rely on a distributed Memcached system and a beastly MySQL database server. Static content is hosted on a cluster of lighttpd servers. Media, such as large files and videos, are hosted (currently) on a server using a minimal Django install using lighttpd plus fastcgi. As of right now were moving toward pushing all media to a service similar to Amazons S3.

當一個使用者�求這個網站，它們會被傳�到Squid (使用lighttpd)的�集主機。在那�，主機會檢查是�使用已經登入。�如�是，他們會招待一個快���。一個已登入的使用者會被引導到一個網站主機(跑著lighttpd加上mod_python(�一個都�有大�的記憶體))構�的�集，��者分散�的Memcached系統和超強的MySQL 資料庫主機。�態的內容是存放在由lighttpd 組�的�集。多媒體，如大的影音檔，通常是放在用超�的Django 加上lighttpd 和 fastcgi。�在這些都移往，推�所有多�體到一個�務，類似Amazons S3。

Christian Hammond :

Christian Hammond

There are two main production servers right now. One is at VMware and consists of an Ubuntu virtual machine running on VMware ESX. We use MySQL for the database, Memcached for our caching back-end, and currently Apache for the Web server. We have several powerful servers that we can scale across when we need to. We may find ourselves moving MySQL or Memcached to another virtual machine as our user base increases.

xDo9EU <a href=”http://yqzawizakcxu.com/“>yqzawizakcxu</a>, [url=http://molcupchkzfm.com/]molcupchkzfm[/url], [link=http://uzvrovlrupbl.com/]uzvrovlrupbl[/link], http://xitnlxuevnvb.com/

The second production server is the one for Review Board itself. The setup is nearly identical to the one at VMware, except the virtual machine is being hosted on VMware Server.

第二个生产�务器就是用于Review Board的那个。它的设置和虚拟机里�的那个是完全一样的，唯一差别就是虚拟机是�行在VMware�务器上的。