Information for: DEVELOPERS   PARTNERS

What to expect while onboarding

Acquia Cloud leverages a stack of technologies specifically tuned to the needs of high-availability enterprise Drupal. Key elements of the stack include:

  • Varnish® and Nginx on a pair of balancers
  • Apache, Memcached, and APC on one or more web servers
  • Gluster shared file system
  • Percona on the database servers
  • Code deployment using Git

Migrating to Acquia Cloud involves making some changes to your application’s code and configuration to leverage these components effectively. For example, to connect to your database, you include a file that is automatically updated by our hosting stack to point to the active database server. In the event that the primary database server becomes unavailable, this file is automatically updated to point to the secondary database server. Other changes are necessary to allow your application to connect to Memcached, and some configuration may be required to allow your application to leverage Varnish properly.

Apart from these basic changes, some applications may require additional effort to bring them in line with best practices. For example, files in nonstandard locations (outside of sites/[site]/files), modules that prevent Varnish from caching, complex .htaccess files, and customizations of how Drupal interacts with the database all may present challenges during onboarding.

Even if your application has been running without issue on other hosting, we recommend you ensure all aspects of your application are fully compatible with Acquia’s platform. If you are developing a new application, we recommend you follow our tips to ensure your build exemplifies best practices from the very beginning.