プッシュプロバイダ
プッシュ通知とメールを送ります。メッセージ単価の課金で、毎秒10,000件。
このページはまだ日本語に翻訳されていません。
The Push Provider stands for Amazon SNS and SES: services that deliver push notifications and email for you.
When to place it#
Place it when you ship the Push notifications Feature on the Team page. Without it, push messages have nowhere to go.
It unlocks with the Notifications Research.
How it works#
Delivery takes a moment, but users do not wait for it. Push messages come in and it links to nothing downstream. It is a Managed Component, so it costs nothing to place, serves every region, and bills for each message. Its throughput limit is high, and each size step doubles it.
Notifications reach it from your code. A Notify request does most of its work asynchronously. With a Queue linked, a Worker sends the push message. Without one, the App Server sends it itself. Link whichever Node sends them to the Push Provider.
How it fails#
Past its limit, it drops messages. With its high limit, that takes a very large audience.
Its cost grows with every message. Watch third-party costs in the Ledger.
Push notifications raise growth and also raise churn a little, because users tire of them. That cost comes from the Feature, not the Component. See Users and growth.
Instance failure#
Signs: The Push Provider's card goes grey, its Inspector reads "The host under this VM died. It still bills.", and the requests sent to it are stranded.
Do now: Press Replace in its Inspector and pay the price. It comes back cold.
Prevent: Place a second Push Provider, so it no longer stands alone.
Zone outage#
Signs: Every Node in one zone goes grey at once.
Do now: Nothing brings the zone back sooner. Fail over promotes a Standby, and this Component keeps none, so it ends on its own after at most 120 s.
Prevent: Research Multiple zones, then put copies in different zones with the Zone setting.
Tips#
Send notifications through a Queue and Workers, so a slow send never holds an App Server slot.
ルール#
- 追加のコピーは 1 つ前より 25% 高くなります。
- 売却すると、最後のコピーの価格の 50% が戻ります。
- サイズは 1 つだけです。