Cloud Platform leverages a stack of technologies specifically tuned to the needs of high-availability enterprise Drupal. Key elements of the stack include:
(Optional) Cloud Platform CDN for global cached content delivery (Fastly)
When migrating to Cloud Platform, you must change your application (glossary term, activate to view definition)’s code and configuration to leverage these components effectively. For example, to connect to your database, you must
Ensuring compatibility with Cloud Platform
Cloud Platform leverages a stack of technologies specifically tuned to the needs of high-availability enterprise Drupal. Key elements of the stack include:
(Optional) Cloud Platform CDN for global cached content delivery (Fastly)
When migrating to Cloud Platform, you must change your application (glossary term, activate to view definition)’s code and configuration to leverage these components effectively. For example, to connect to your database, you must
maintained by Acquia that points to the active database node (glossary term, activate to view definition), regardless of what environment (glossary term, activate to view definition) the code is used in. If your primary database node becomes unavailable, this configuration redirects database queries to the secondary database node.
Your application may require additional changes to connect to Memcached or to leverage Varnish for improved performance.
Apart from these basic changes, some applications may require more effort to bring them in line with best practices. For example:
Files in nonstandard locations (outside of sites/[site]/files)
Customizations of how Drupal interacts with the database
Any of these items may present challenges during onboarding.
Even if your application has been running without any issue on other hosting platforms, Acquia recommends you to ensure that all aspects of your application are fully compatible with Acquia’s platform. If you’re developing a new application, use Acquia’s tips to ensure that your build follows best practices from the beginning.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
maintained by Acquia that points to the active database node (glossary term, activate to view definition), regardless of what environment (glossary term, activate to view definition) the code is used in. If your primary database node becomes unavailable, this configuration redirects database queries to the secondary database node.
Your application may require additional changes to connect to Memcached or to leverage Varnish for improved performance.
Apart from these basic changes, some applications may require more effort to bring them in line with best practices. For example:
Files in nonstandard locations (outside of sites/[site]/files)
Customizations of how Drupal interacts with the database
Any of these items may present challenges during onboarding.
Even if your application has been running without any issue on other hosting platforms, Acquia recommends you to ensure that all aspects of your application are fully compatible with Acquia’s platform. If you’re developing a new application, use Acquia’s tips to ensure that your build follows best practices from the beginning.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform