Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The cache architecture in Drupal 8 changed fundamentally. E.g., rendered elements (such as regions, blocks and fields) are now responsible for specifying cacheability metadata. Thus there is no need to explicitly specify this data manually anymore (this was one part of Authcache). Also core ships with the BigPipe module. It can be used to deliver per-user fragments outside of the regular page-rendering process (this is the other part where Authcache shines for Drupal 7). Thanks to the cacheability metadata this can be done without any additional configuration.
As a result most if not all of Authcache is superseded by built-in core functionality.
Comments
Comment #1
julianmancera CreditAttribution: julianmancera commentedHi all,
I'm also wondering about any plan for this module in drupal 8. Let us know to get hands into it.
Thank you
Julian
Comment #2
znerol CreditAttribution: znerol commentedThe cache architecture in Drupal 8 changed fundamentally. E.g., rendered elements (such as regions, blocks and fields) are now responsible for specifying cacheability metadata. Thus there is no need to explicitly specify this data manually anymore (this was one part of Authcache). Also core ships with the BigPipe module. It can be used to deliver per-user fragments outside of the regular page-rendering process (this is the other part where Authcache shines for Drupal 7). Thanks to the cacheability metadata this can be done without any additional configuration.
As a result most if not all of Authcache is superseded by built-in core functionality.