Difference between revisions of "Platform Deployment Options"
From LongJump Support Wiki
imported>Aeric m (Text replace - 'Category:System Administration' to 'Category:Installation') |
imported>Aeric |
||
| Line 11: | Line 11: | ||
;Multiple <tt>memcached</tt> servers:The MemCache Daemon can also be run on one or more separate servers. In addition to the performance improvement, that configuration makes it somewhat easier to add LongJump servers to scale capacity later. ''Learn More:'' [[Configuring memcached]] | ;Multiple <tt>memcached</tt> servers:The MemCache Daemon can also be run on one or more separate servers. In addition to the performance improvement, that configuration makes it somewhat easier to add LongJump servers to scale capacity later. ''Learn More:'' [[Configuring memcached]] | ||
;Separate Database Server:Running the LongJump application and the Database on different servers is highly recommended for a production deployment. ''Learn More:'' [[Configuring MySQL | ;Separate Database Server:Running the LongJump application and the Database on different servers is highly recommended for a production deployment. ''Learn More:'' [[Configuring MySQL to Run on a Separate Server]] | ||
;Separate Servers for Backend Processes:The backend processes that make up the LongJump application can be (and should be) deployed to at at least one "backend server" to minimize response time in the customer-facing server they would otherwise be running on. Beyond that, heavily-used services can be deployed to servers of their own, to maximize performance. ''Learn More:'' [[Managing Backend Services]] | ;Separate Servers for Backend Processes:The backend processes that make up the LongJump application can be (and should be) deployed to at at least one "backend server" to minimize response time in the customer-facing server they would otherwise be running on. Beyond that, heavily-used services can be deployed to servers of their own, to maximize performance. ''Learn More:'' [[Managing Backend Services]] | ||
[[Category:Installation]] | [[Category:Installation]] | ||
Revision as of 17:07, 7 June 2011
Platform Deployment Options
This section describes deployment options that increase scalability and reliability.
- Multiple LongJump Servers
- Instances of LongJump can be deployed on different servers to improve response times.
- Separate servers for Apache httpd
- When the Apache httpd server is used to serve static content, the Apache httpd instances can be deployed on separate servers, while LongJump instances run on their own servers. Learn More: Configuring Apache to Serve Static Content
- Web App Accelerators
- Web Application acceleration services like those provided by Akamai can also be used to improve response times and throughput. Learn More: Web Application Accelerator.
- Multiple memcached servers
- The MemCache Daemon can also be run on one or more separate servers. In addition to the performance improvement, that configuration makes it somewhat easier to add LongJump servers to scale capacity later. Learn More: Configuring memcached
- Separate Database Server
- Running the LongJump application and the Database on different servers is highly recommended for a production deployment. Learn More: Configuring MySQL to Run on a Separate Server
- Separate Servers for Backend Processes
- The backend processes that make up the LongJump application can be (and should be) deployed to at at least one "backend server" to minimize response time in the customer-facing server they would otherwise be running on. Beyond that, heavily-used services can be deployed to servers of their own, to maximize performance. Learn More: Managing Backend Services