TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: When would you go with Kinesis over SNS/SQS and why?

4 点作者 1penny42cents超过 3 年前
In a previous project we went with SNS&#x2F;SQS for our event bus, because of simplicity. I wondered towards the end if Kinesis would have been better.<p>The main reason in my mind being one less API&#x2F;component, ordered streams, and replayability. SNS&#x2F;SQS made it a bit painful to replay events. The counterpoint seems that Kinesis has some complexity around scalability that you might not need to worry about, depending on the usage.<p>But I&#x27;ve never used Kafka&#x2F;Kinesis so I can&#x27;t say. What are your thoughts?

2 条评论

nivertech超过 3 年前
<p><pre><code> Message Brokers: - Amazon SNS + Mobile push notifications - Amazon SQS - Amazon EventsBridge - Amazon MQ for RabbitMQ - Amazon MQ for Apache ActiveMQ Pub&#x2F;Sub: - AWS IoT Core for managed MQTT message broker - Amazon ElastiCache for Redis Append Only Logs: - Amazon Managed Streaming for Apache Kafka (Amazon MSK) - AWS Kinesis Data Streams - AWS Kinesis Data Firehose New RabbitMQ will have Append-Only Logs via RabbitMQ Streaming - not sure AWS already supports this Same for Redis Streams - not sure Amazon ElastiCache for Redis already supports this</code></pre>
评论 #28636879 未加载
fiftyacorn超过 3 年前
I think the comparison of sqs&#x2F;sns Vs eventbridge sounds more like what your mean<p>I find eventbridge gives better decoupling than sqs and is easier to configure