Relied on the existing single-machine plus persistent-volume deployment shape to reject a separate serverless function and keep the scheduled job next to the database file. No new vendor or pipeline was needed; assessment came from project configuration rather than live deployment actions.
- What worked
- The always-on machine and volume model made the scheduling tradeoff clear and kept data locality simple.
