AgileApps Support Wiki Pre Release

Difference between revisions of "Platform Deployment Options"

From AgileApps Support Wiki
imported>Aeric
m (Text replace - 'Category:System Administration' to 'Category:Installation')
 
imported>Aeric
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Platform Deployment Options===
<includeonly>===Platform Deployment Options===</includeonly>
This section describes deployment options that increase scalability and reliability.


This section describes deployment options that increase scalability and reliability.
;Multiple Application Servers:Instances of the platform can be deployed on different servers to improve response times.


;Multiple LongJump Servers:Instances of LongJump can be deployed on different servers to improve response times.
;Separate servers for Apache <tt>httpd</tt>:When the Apache <tt>httpd</tt> server is used to serve static content, the Apache <tt>httpd</tt> instances can be deployed on separate servers, while platform instances run on their own servers. ''Learn More:'' [[Installing and Configuring Apache for Use with the Platform]]


;Separate servers for Apache <tt>httpd</tt>:When the Apache <tt>httpd</tt> server is used to serve static content, the Apache <tt>httpd</tt> instances can be deployed on separate servers, while LongJump instances run on their own servers. ''Learn More:'' [[Configuring Apache to serve static content from LongJump |Configuring Apache to Serve Static Content]]
;Separate Messaging Server:To further improve performance, the Messaging Server can be installed on a standalone system. Or it can run the same system as an appserver.


;Web App Accelerators: Web Application acceleration services like those provided by Akamai can also be used to improve response times and throughput. ''Learn More:''  [http://www.akamai.com/html/technology/products/waa.html Web Application Accelerator].
;Web App Accelerators: Web Application acceleration services like those provided by Akamai can also be used to improve response times and throughput. ''Learn More:''  [http://www.akamai.com/html/technology/products/waa.html Web Application Accelerator].


;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 application servers to scale capacity later. ''Learn More:'' [[Configuring memcached]]
 
;Certificate-authentication Server:
:Adding a certificate-validation server to the network architecture, allows the platform to be accessed by browsers or by REST APIs without a login step, by supplying an identifying certificate.
:''Learn more:'' {{^Article Client Certificates}}


;Separate Database Server:Running the LongJump application and the Database on different servers is highly recommended for a production deployment. ''Learn More:'' [[Configuring MySQL and LongJump to Run on Separate Servers]]
;Separate Database Server:Running the platform 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 used by the application server 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]]
<noinclude>


[[Category:Installation]]
[[Category:Installation]]
</noinclude>

Latest revision as of 20:51, 15 July 2015

This section describes deployment options that increase scalability and reliability.

Multiple Application Servers
Instances of the platform 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 platform instances run on their own servers. Learn More: Installing and Configuring Apache for Use with the Platform
Separate Messaging Server
To further improve performance, the Messaging Server can be installed on a standalone system. Or it can run the same system as an appserver.
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 application servers to scale capacity later. Learn More: Configuring memcached
Certificate-authentication Server
Adding a certificate-validation server to the network architecture, allows the platform to be accessed by browsers or by REST APIs without a login step, by supplying an identifying certificate.
Learn more: Client Certificate Authentication in a private AgileApps Cloud (pdf)
Separate Database Server
Running the platform 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 used by the application server 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