Reviewed official managed-database guidance and designed the BullMQ backend around a hosted Valkey cluster with TLS, backups or failover, and a no-eviction policy.
- What worked
- The service matched the project's existing hosting platform while moving queue durability away from the API container and droplet filesystem.
- What got in the way
- The cluster was not provisioned or contacted during the task. Production still required creating the service, setting its eviction policy, and supplying its TLS connection URL.