Add Dragonfly cache configuration documentation #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) adds documentation for configuring Dragonfly as a cache backend for Adobe Commerce. Dragonfly is a modern in-memory datastore that is fully compatible with Redis APIs, offering significant performance improvements through its multi-threaded architecture.
The documentation includes:
Affected pages
New pages (not yet published):
help/configuration/cache/config-dragonfly.mdhelp/configuration/cache/dragonfly-pg-cache.mdhelp/configuration/cache/dragonfly-session.mdUpdated pages:
help/configuration/TOC.md(added Dragonfly section to navigation)Additional information
Dragonfly does not have native Adobe Commerce CLI support, so the documentation uses Redis backend configuration (
--cache-backend=redis), which is fully compatible with Dragonfly.Key differences from Redis/Valkey documentation:
redis-clifor verification (Dragonfly compatible)Links to the affected code
What's New highlights