Short answer: choose private object storage for normal user documents and generated exports when a one-day expiration window is acceptable; keep a database record and separate backups beside it. Choose an immutable archive instead when legal hold, hourly expiry, or WORM retention is a requirement.
Two system shapes for an edtech document pipeline
The application here stores training artifacts: uploaded assignments, generated certificates, and export bundles. The decision is less about a brand than about where the retention contract lives.
Shape Invariant Pick it when Trade-off
Private object storage plus lifecycle rules An object key and a database row describe the same artifact; expiration is at least 1 day Normal app documents, temporary files, and old exports No hourly expiry, object lock, or version history
Archive service plus application index The archive owns immutable retention and legal-hold state; the app stores a pointer and audit record Regulated records, litigation holds, or strict recovery…