You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Apache Wiki <wi...@apache.org> on 2011/12/31 16:31:10 UTC

[Httpd Wiki] Trivial Update of "PerformanceScalingOut" by PeteHouston

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The "PerformanceScalingOut" page has been changed by PeteHouston:
http://wiki.apache.org/httpd/PerformanceScalingOut?action=diff&rev1=3&rev2=4

Comment:
typo fix s/en/and/

  Scaling out your web site is a mixed blessing. While you get to serve more
  transactions and, presumably, do more business, the additional hardware, software
  and network segments will also give you more intricacies to oversee. You
- get to manage, maintain en secure a farm of servers instead of just one. The
+ get to manage, maintain and secure a farm of servers instead of just one. The
  configuration of your servers, and application software and content design will
  be highly influenced by the infrastructure design decisions you make, and they
  will be heavily intertwined. However, with judicious planning, scaling out can

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org