TL;DR NAS is the right home for data that applications open, lock and edit in place. Object storage is the right home for data written once and read many times, at a scale where one filesystem namesp

Markdown supported · ⌘↵ to post
When comparing NAS with S3-compatible object storage, how should teams calculate the total cost of ownership for data engineering workloads, considering request charges, egress, compute costs, and data retrieval frequency?
StackShortlist
Proof Over Promises.
The Object Lock row in the checklist is the one that bites people later. Since it can only be set at bucket creation, deciding retention mode before the first upload saves a full copy to a new bucket. The point about counting objects and not just terabytes is a good one too. A small-file tail can hit metadata limits on a NAS long before the disks are full.