Difference between revisions of "Additional Deployment Options"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 2: | Line 2: | ||
To further improve the performance of the system, data safety and data security, there are some additional things you can do: | To further improve the performance of the system, data safety and data security, there are some additional things you can do: | ||
:* '''Send database backups to a distant, remote server.'''<br>Keep the ''replicated database'' on premise, for instant failover when needed. But for disaster recovery, keep the ''backup database'' | :* '''Send database backups to a distant, remote server.'''<br>Keep the ''replicated database'' on premise, for instant failover when needed. But for disaster recovery, keep the ''backup database'' 1000 miles away, or more. | ||
:*''' Allow only the backup server to connect to the backup port.'''<br>In addition to requiring the username and password to connect to the backup port, allow connections only from a specific IP address. | :*''' Allow only the backup server to connect to the backup port.'''<br>In addition to requiring the username and password to connect to the backup port, allow connections only from a specific IP address. | ||
| Line 9: | Line 9: | ||
:* Add [http://www.scaledb.com/pdfs/ArchitecturePrimer.pdf Database Clustering].<br>With a database cluster, the application server sees a single database, but inside the cluster many database servers are at work. | :* Add [http://www.scaledb.com/pdfs/ArchitecturePrimer.pdf Database Clustering].<br>With a database cluster, the application server sees a single database, but inside the cluster many database servers are at work. | ||
{{Note|All of those options are in effect in the public cloud installation of the {{EnterpriseBrand}}, with the exception of database clustering. (So far, the performance profile has not required it, despite having thousands of users on the system.)}} | |||
Revision as of 18:43, 29 June 2015
To further improve the performance of the system, data safety and data security, there are some additional things you can do:
- Send database backups to a distant, remote server.
Keep the replicated database on premise, for instant failover when needed. But for disaster recovery, keep the backup database 1000 miles away, or more.
- Send database backups to a distant, remote server.
- Allow only the backup server to connect to the backup port.
In addition to requiring the username and password to connect to the backup port, allow connections only from a specific IP address.
- Allow only the backup server to connect to the backup port.
- Add a Dynamic Site Accelerator--in effect, a giant cache in the cloud
For example, use the Akamai accelerator.
- Add a Dynamic Site Accelerator--in effect, a giant cache in the cloud
- Add Database Clustering.
With a database cluster, the application server sees a single database, but inside the cluster many database servers are at work.
- Add Database Clustering.
Note: All of those options are in effect in the public cloud installation of the AgileApps Cloud platform, with the exception of database clustering. (So far, the performance profile has not required it, despite having thousands of users on the system.)
