Update:Archive/2.0/Architecture and General Design/Infrastructure: Difference between revisions
(Added note about Squirm) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
[[Update:Home_Page|Update: Home Page]] » Infrastructure | [[Update:Home_Page|Update: Home Page]] » [[Update:Architecture_and_General_Design|Architecture and General Design]] » Infrastructure | ||
== Introduction == | == Introduction == | ||
Revision as of 19:54, 22 January 2005
Update: Home Page » Architecture and General Design » Infrastructure
Introduction
This page will describe the UMO infrastructure supporting the UMO service.
Caching
We are currently using Squid for caching of images and content. This has been quite scalable but we need to start considering using Apache2 + mod_cache/mod_proxy to be able to handle more types of HTTP 1.1 requests.
We may want to consider using Squirm as part of Squid to handle certain caching situations. See my proposal in bug 279379 for one. It may also be useful for load balancing. --Luser 11:51, 22 Jan 2005 (PST)
Database
We are using MySQL 4.0.22 for the database. Moving forward, we will be looking at using MySQL 4.1.x in order to take advantage of subselects. We currently have this all on one database server but moving forward we need to consider a master/slave arrangement for redundancy sake.
Web/Application Servers
We are using Apache2 + PHP 4 on top of Linux machines right now. Right now, we only have one application server and we need to fix that asap. The current application server is running RHEL 3.