Modules and applications incompatible with Cloud Platform
Due to Cloud Platform’s security and permissions requirements, you may experience incompatibilities with some applications and Drupal contributed modules.
Requires subscribers to replace Acquia’s default VCL with a companion custom Varnish configuration. Since Cloud Platform does not support this replacement, you cannot use this module with Cloud Platform.
Modules and applications incompatible with Cloud Platform
Due to Cloud Platform’s security and permissions requirements, you may experience incompatibilities with some applications and Drupal contributed modules.
Requires subscribers to replace Acquia’s default VCL with a companion custom Varnish configuration. Since Cloud Platform does not support this replacement, you cannot use this module with Cloud Platform.
Stores data on a per-infrastructure basis, which can lead to different data being served by different infrastructure. It also uses memory that would otherwise be used by OPcache. As an alternative, you can use Memcached.
Does not have compatibility with Cloud Platform, specifically the File Conveyor sub-module. The distributed file system used by Cloud Platform Enterprise does not support inotify, which is required for operation. This is related to CDNs and you can use the Origin Pull mode.
Leverages the W3C standard to enable high-performance caching by substituting personalized page content with a generic <esi:include> tag, thus allowing reverse-proxies (like Varnish) to cache the main page, and subsequently fetch and merge the personalized ESI content at the edge. Cloud Platform does not support Edge Side Includes (ESI).
Sets session cookies for anonymous visitors using pages that contain H5P elements. This bypasses Varnish caching in all future requests for those anonymous users.
Has limited updates from developers. As an alternative, you can use the Memcache API and Integration module, which integrates with Acquia’s memcached implementation.
Causes Drupal to output large HTTP headers. This causes errors of type 500 that are difficult to troubleshoot. As an alternative, you can use the Acquia Purge module.
Requires session cookies to be set, preventing Varnish from caching pages. When using this module, cron can run intense queries to join the session and session_api tables, causing major slowdowns.
Attempts to replicate the effort of the Varnish Cache that is already available in Cloud Platform applications. It does not work with Cloud Platform applications because it requires connections to load balancers that are not provided by Acquia. The Varnish caching provided by Acquia works out-of-the-box as long as you use caching.
Stores data on a per-infrastructure basis, which can lead to different data being served by different infrastructure. It also uses memory that would otherwise be used by OPcache. As an alternative, you can use Memcached.
Does not have compatibility with Cloud Platform, specifically the File Conveyor sub-module. The distributed file system used by Cloud Platform Enterprise does not support inotify, which is required for operation. This is related to CDNs and you can use the Origin Pull mode.
Leverages the W3C standard to enable high-performance caching by substituting personalized page content with a generic <esi:include> tag, thus allowing reverse-proxies (like Varnish) to cache the main page, and subsequently fetch and merge the personalized ESI content at the edge. Cloud Platform does not support Edge Side Includes (ESI).
Sets session cookies for anonymous visitors using pages that contain H5P elements. This bypasses Varnish caching in all future requests for those anonymous users.
Has limited updates from developers. As an alternative, you can use the Memcache API and Integration module, which integrates with Acquia’s memcached implementation.
Causes Drupal to output large HTTP headers. This causes errors of type 500 that are difficult to troubleshoot. As an alternative, you can use the Acquia Purge module.
Requires session cookies to be set, preventing Varnish from caching pages. When using this module, cron can run intense queries to join the session and session_api tables, causing major slowdowns.
Attempts to replicate the effort of the Varnish Cache that is already available in Cloud Platform applications. It does not work with Cloud Platform applications because it requires connections to load balancers that are not provided by Acquia. The Varnish caching provided by Acquia works out-of-the-box as long as you use caching.
Cloud Platform