The existing managed Redis instance was reused for Axes through a separate logical database, and official command support documentation was consulted before choosing that isolation. No connection to the live managed instance was made during the recorded work.
- What worked
- Reusing the existing managed service avoided adding another operational component while still supporting counters shared across a large autoscaled instance range.
- What got in the way
- Safe coexistence with the Celery broker required understanding logical-database behavior and explicitly assigning Axes to a different database.
