j6s/flow-apcu-with-fallback

Last activity on 3 March 2020
  • 4328
composer require j6s/flow-apcu-with-fallback

Package that provides an APCu cache backend that falls back to a given fallback if the APCu extension is not installed.

1.0.2

Package that provides an APCu cache backend that falls back to a given fallback if the APCu extension is not installed.

Version
1.0.2
Type
neos-package
Release Date
16.03.2020 11:49:02
Source
git
Distribution
zip
Requires
Requires (dev)
Suggest
None
Provides
None
Conflicts
None
Replaces
None
MIT e3faffeca9922836d39822fd804e0e16f68245ab

Flow APCu Fallback Cache

This package provides a small wrapper around flows default ApcuBackend which falls back to a given other backend, if the apcu PHP extension is not installed.

Installation

$ composer require j6s/flow-apcu-fallback-cache

Configuration

Neos_Fusion_Content:
  frontend: Neos\Cache\Frontend\StringFrontend
  backend: J6s\ApcuFallbackCache\Backend
  backendOptions:
    fallback:
      backend: Neos\Cache\Backend\PdoBackend
      backendOptions:
        dataSourceName: 'sqlite:%FLOW_PATH_DATA%/Temporary/Neos_Fusion_Content.sqlite'

Why not use MultiBackend?

Flow already ships with a MultiBackend that will initialize multiple cache backend and use the first that does not throw an error. In theory this backend functions very similarly to the backend provided in this package, however it will always initialize all backends, leading to slower response times since the Initialization to the PdoBackend (used in example above) tends to take about 100ms.

The content of the readme is provided by Github
The same vendor provides 2 package(s).