オブジェクトストレージ
アップロードされたファイルを保持します。上限はありません。保存した分だけ課金されます。
このページはまだ日本語に翻訳されていません。
Object Storage stands for Amazon S3: a store for files that grows without limit.
When to place it#
Place it when uploads and video load the Database: its CPU and latency climb as the Upload or Video share of the mix grows. It unlocks with Object storage.
Add a CDN once you serve video.
Check its Burn in the Ledger as the Company ages, because it only grows.
The Slow Uploads Sandbox shows a slow upload holding an App Server slot.
サンドボックス遅いアップロードApdexを0.9以上に90秒間保ってください。How it works#
It has no capacity limit, and each request waits for the first byte, which is slower than a database query. Object puts and gets arrive carrying uploaded files and video, and no Component sits behind it. See object storage.
Its Burn grows with the data it holds, and that data never shrinks. Every upload adds to it.
Until you link Object Storage, the Database stores files as rows. When an App Server links to both, files go to Object Storage, and the Database stops taking them.
Options#
| 設定項目 | 設定値 | 表示条件 |
|---|---|---|
| 製品 | S3 / R2 | 常時 |
| クラス | 標準 / 低頻度アクセス / アーカイブ | 常時 |
| ライフサイクル | オフ / 30 d / 90 d / 365 d | 常時 |
Product. The store is S3, or R2 with Egress optimization. R2 has no egress to the internet, and a read waits a little longer for its first byte unless a CDN is on the board. Every read and write also bills per request, at its product's price.
Storage class. The class sets what the bytes cost to keep, and what they cost to read back.
| Class | Storage price | Reading it back |
|---|---|---|
| Standard | Full price | At once. |
| Infrequent access | Half price | At once, and a retrieval fee per GB, on the same bill line. |
| Archive | A tenth of it | Only after a restore. A media request fails as timeout meanwhile. |
Infrequent access suits files that are written once and rarely read. Archive suits the ones kept only because a rule says so. Neither is free to read, because the retrieval fee and the restore are the price of the cheaper storage. The Inspector and Data tier hold the prices.
Lifecycle. Lifecycle rules move objects on their own once they are old enough. Each object past the window drops one class, from Standard to Infrequent access and from Infrequent access to Archive. A store that has been filling for a while holds most of its bytes in the cheaper class, and the oldest share of its reads fails as a timeout until those objects are restored. The Inspector shows how much of the store is past the window, and Data tier holds the rule.
How it fails#
Object Storage does not overload or fail on its own in the game. Its problems are latency and cost.
First-byte latency adds to every video and upload. A CDN answers most video at the edge.
Storage Burn only grows. Check it in the Ledger as the Company ages.
A slow upload holds an App Server slot while the file comes up the wire. Send uploads through a Queue so the App Server keeps only the short sync part.
Region outage#
Signs: Every Node in one region goes grey at once, and that region's board goes grey with them.
Do now: Nothing speeds it up. Fail over moves only Nodes that hold no data, so this one stays down until the incident ends: 180 sim seconds in the catalog, 60 once the error budget counts. A store spread across regions needs nothing from you.
Prevent: Research Multiple regions and GeoDNS, then run a copy of it in a second region.
Tips#
Pair Object Storage with a CDN once you serve video.
Link Workers to Object Storage when you send uploads through a Queue.
ルール#
- 追加のコピーは 1 つ前より 25% 高くなります。
- 売却すると、最後のコピーの価格の 50% が戻ります。
- サイズは 1 つだけです。
一緒に使えるもの#
次に取るリサーチ#
オブジェクトストレージを手に入れると、次のリサーチがそれを土台に進みます。