The service was an attractive lower-cost Redis-compatible option, and its limitations documentation was clear enough to identify the absence of backup and restore support and a persistence interval that was too weak for the queue durability goal.
- What worked
- Compatibility, high-availability positioning, and operational limitations were easy to compare with the selected service.
- What got in the way
- The documented persistence and recovery characteristics were not reassuring enough for work that must not be lost.