Difference between revisions of "Design Specs: Scalability"
From WormBaseWiki
Jump to navigationJump to search (New page: == Objectives == To build a robust and scalable platform for hosting the next generation of the WormBase website. == Current Status == As of Jan 2010, the WormBase website resides on a ...) |
|||
| Line 3: | Line 3: | ||
To build a robust and scalable platform for hosting the next generation of the WormBase website. | To build a robust and scalable platform for hosting the next generation of the WormBase website. | ||
| − | == Current | + | == Limitations of the Current System == |
| − | As of Jan 2010, the WormBase website resides on a heterogeneous cluster of | + | As of Jan 2010, the WormBase website resides on a heterogeneous cluster of web and database servers. A single server running the squid reverse proxy software load balances across these servers. |
| − | Although this system scales easily, it is not ideal for the following reasons. | + | Although this system scales easily and has served WormBase well for six years, it is not ideal for the following reasons. |
| − | 1. Multiple single points of redundancy | + | 1. Multiple single points of redundancy that require manual intervention to resolve |
| − | 2. Difficulty of configuration and management | + | 2. Difficulty of configuration and management of reverse proxy software |
| − | 3. Lack of true fault tolerance | + | 3. Lack of true fault tolerance in system |
| + | |||
| + | 4. Heterogeneity complicates management, backups, production releases | ||
Revision as of 20:34, 2 February 2010
Objectives
To build a robust and scalable platform for hosting the next generation of the WormBase website.
Limitations of the Current System
As of Jan 2010, the WormBase website resides on a heterogeneous cluster of web and database servers. A single server running the squid reverse proxy software load balances across these servers.
Although this system scales easily and has served WormBase well for six years, it is not ideal for the following reasons.
1. Multiple single points of redundancy that require manual intervention to resolve
2. Difficulty of configuration and management of reverse proxy software
3. Lack of true fault tolerance in system
4. Heterogeneity complicates management, backups, production releases
