We just launched Amazon SNS FIFO topics

aws.amazon.com

10 points·otaviofff··7 comments

Open articleView on HN

Pricing vs standard SNS topics, from https://aws.amazon.com/sns/pricing/

Standard topics:

> First 1 million Amazon SNS requests per month are free, $0.50 per 1 million requests thereafter

FIFO topics:

> Publish API requests are $0.30 per 1 million and $0.017 per GB of payload data

> Subscription messages are $0.01 per 1 million and $0.001 per GB of payload data

where

> Subscription messages are calculated by multiplying the number of published messages and the number of subscriptions. Both filtered and delivered messages count towards the number of subscription messages.

Is SNS just hosted Nchan?

https://nchan.io

Please, let me know your comments =)

The public TPS for SNS FIFO topics are noted as soft limit on https://docs.aws.amazon.com/general/latest/gr/sns.html. Is that really a soft limit which can be increased? How do the maximum possible TPS compare with SNS standard topics?

Congrats. I still wish it was more ergonomic to build a fan out architecture where clients pull messages out of a queue with AWS. Basically a long-poll style SNS queue.

Thanks! I’m curious. How is your suggestion different from fanning out messages from the SNS topic, then polling the SQS queues subscribed to the topic?

SQS doesn’t have the model where the lifetime of the queue is tied to the subscriber, so if you have 1000 subscribers to a single sqs queue, you end up having to go sqs -> sns -> 1000 client created sqs queues. You end having to write code to garbage collect these queues and each message has to be written 1001 times.

Reply on news.ycombinator.com