Short answer: To store user-uploaded documents in a Node.js backend, keep bounded small files and metadata in one database transaction; when large-file traffic and recovery need independence, separate relational metadata from object storage.
Storing document bytes in a relational database is reasonable when files are small, access follows the same authorization path as ordinary rows, and operational simplicity matters more than isolating file traffic. For most growing upload systems, searchable metadata and ownership state can remain relational while immutable bytes move to object storage. The cheapest backend is the one whose backup, restore, deletion, and failure behavior the team can actually operate; a low storage rate does not settle that question.
This is an architecture decision, not a vendor comparison. The deciding evidence should come from the workload: file-size distribution, upload concurrency, download traffic, retention rules, recovery objectives, and the people who will be on call.β¦