Recommendation

需要成熟生态时从 Amazon S3 开始;已在 Cloudflare 架构内且出口成本敏感时评估 R2。

先定义谁能上传和读取、文件如何失效、媒体从哪里交付,再比较 S3 兼容性与边缘集成。12

适用范围: Application and platform teams storing user files, media, exports, backups, archives, or application objects

Main trade-off

兼容性和生态通常意味着更多配置;边缘一体化降低运维,但增加平台集中度。1245

选择标准

按真实约束逐项判断,不要只比较功能列表。

  1. Object lifecycle

    Define retention, versioning, deletion, legal hold, archival, replication, restore, and lifecycle transitions.12

  2. Access and security

    Choose public versus private objects, service identity, signed access, encryption, audit, tenant isolation, and policy ownership.12

  3. Region and delivery

    Set residency, latency, CDN, transformation, download, cross-region, and disaster-recovery requirements.23

  4. Workload economics

    Model stored bytes, object count, operations, retrieval, transfer, replication, storage classes, and adjacent-service charges.1

适用路线

这些条件会改变默认答案;请在作出承诺前逐项验证。

AWS breadth and controls are required

Evaluate Amazon S3.

Regions, storage classes, lifecycle, policy, compliance, and AWS integrations support broad object-storage needs.

Verify: Request, retrieval, transfer, replication, storage-class, and adjacent-service charges require workload-specific modeling.12

Cloudflare delivery economics lead

Evaluate Cloudflare R2.

Cloudflare integration and S3-compatible access can fit delivery-heavy applications with a deliberate Cloudflare boundary.

Verify: Feature, region, operation, ecosystem, and compatibility differences mean R2 cannot be treated as S3 with different pricing.123

Supabase is the intentional backend

Evaluate Supabase Storage.

Shared identity, Postgres policies, database, and storage tooling can simplify access control and platform operations.

Verify: Storage policy, quotas, delivery, data movement, and pricing become part of the wider Supabase commitment.124

A storage-first cost profile fits

Evaluate Backblaze B2.

A narrower object-storage service can fit backup, archive, media, and application objects without the full AWS platform surface.

Verify: Verify regions, API behavior, lifecycle, delivery integrations, service breadth, and download economics.125

边界: File Upload Workflows owns client ingestion, authorization, validation, progress, resumability, processing, and handoff. CDN and media delivery are downstream concerns.

关键差异

把真正会改变决策的边界单独比较。

Policy model
Identity, bucket policy, row-level integration, signed access, and tenant isolation differ materially.23
Lifecycle
Versioning, storage classes, retention, restore, replication, and deletion controls shape durable operation.12
Delivery
CDN integration, transformations, transfer charging, origin access, and cache behavior affect end-to-end design.23
Compatibility
S3-compatible APIs vary in supported operations, authentication, tooling, events, and ecosystem integrations.12
Cost
Storage alone is insufficient; model requests, retrieval, transfer, replication, minimums, and adjacent services.12

官方资源

官方文档与继续决策的正式路径。

来源

支撑页面关键主张的资料。

  1. 1
    Amazon S3 user guide

    Amazon Web Services · Accessed Official

  2. 2
    Cloudflare R2 documentation

    Cloudflare · Accessed Official

  3. 3
    R2 S3 compatibility

    Cloudflare · Accessed Official

  4. 4
    Supabase Storage documentation

    Supabase · Accessed Official

  5. 5
    Backblaze B2 documentation

    Backblaze · Accessed Official