Acquia Cloud vs WP Engine

Acquia Cloud is the premier hosting provider for Drupal while WP Engine is the web hosting leader for WordPress. We compare the two platforms.

acquia cloud versus WP Engine

Acquia Cloud is the premier hosting provider for Drupal while WP Engine is the web hosting leader for WordPress. Drupal and WordPress are architecturally quite different. In this post we look at how these differences manifest in their respective hosting providers.

First, a brief nod to how functionally similar they are. Both provide almost identical devops functionality: multiple environments, backup, restoration, archiving, SSL enablement and code management. Here is a screenshot of the WP Engine  and Acquia Cloud dashboard:

WP engine overview
acquia loud overview

Clearly, an amazing amount of overlap!

Initial Site Setup

Perhaps the biggest difference between the two platforms is how differently they approach the initial site setup. Acquia Cloud offers a downloadable desktop app (Link).

acquia desktop app

When you start the application, it shows three options: start a Drupal instance from scratch, start with a local Drupal site or start with a Drupal site on the Acquia cloud. A quick couple of steps involving SSH key setups and voila! – you are up and running.

aquia desktop dev app

In contrast, the process for getting a WordPress instance running on WPEngine is a little bit more complicated. We can either use plugins such as All in one WP Migration and Duplicator or do it manually. Either way, it is not as simple and elegant as Acquia’s approach.

exemplifi winscp

Code Management

Acquia Cloud lets a user manage the code, files and database separately. In contrast, all of this is managed as a single entity within WP Engine.

acquia cloud overview

Acquia Cloud allows more granular control. For eg. you can move the code from dev to stage, but not the database. This is much harder to achieve in WPEngine. Another minor difference is that Acquia does not allow code pushes directly to stage or production environments — it has to go through the dev environment. WPEngine is more lax in this matter.

Database Versions

Both WP Engine and Acquia offer a phpmyadmin interface to manage database related operations: importing, exporting and running SQL queries. The big difference is that Acquia also offers automatic backup and restore of the database.

database versions of wepengine backups

PHP Versions

WP Engine maintains a very tight coupling between WordPress and the PHP version. When either of them change, WP Engine automatically updates both of them.  Acquia cloud on the other hand, gives the flexibility to select PHP versions separately from the Drupal instance. Drupal 7 for example can run on older PHP versions while Drupal 8 runs on newer versions.

php versions of backups
php backups supported in wpengine

Scheduled Jobs

Acquia cloud provides the facility to run scheduled cron jobs. Although Drupal has this native capability, Acquia’s scheduled jobs are more reliable also support integrated logging for all applications running on it.

WordPress has native capabilities via wp-cron but it is not as robust. Although WPEngine has this cron job functionality in the backend, one has to request the support team to set it up.

scheduling jobs screen

Redirect Rules

Redirect rules automatically guide visitors away from old or expired links. WPEngine provides a simple interface to manage these 301 and 302 redirects without the need to configure additional plugins or edit the .htaccess file manually.

redirect rules in wpengine

Site Migration

Moving sites from one provider to another is a big deal and usually involves a lot of work. WPEngine provides an easy-to-use migration utility that builds on BlogVault. Simply install the plugin in the destination environment, provide the sftp details to WPEngine and the work gets done in a single click.

website migration screenshot
website migration status
website migration success screen

Acquia Cloud has its Site Factory capability but it doesn’t provide such an elegant single-click capability and involves a lot more steps.

Further Reading

Related Insights

Internationalization in Drupal

We look at the basics of how to launch multilingual sites in Drupal.

Ani Mahant

Drupal

Component Design in Drupal

In an earlier post, we had introduced component-based front-end design for websites. We discussed how essential it is, to ensure coherence, consistency and productivity when building large websites. In this post, we discuss component-based design approaches in Drupal.

Ani Mahant

Drupal

Guidelines for a Drupal 6 to Drupal 8 Migration

Migrating from Drupal 6 to Drupal 8 is tricky business. We outline a couple of approaches, discuss multilingual considerations and review a few gotchas.

Vinod Pabba

Drupal

Subscribe to our newsletter