Need advice about which tool to choose?Ask the StackShare community!

Amazon SQS

2.9K
2K
+ 1
171
Apache Pulsar

114
195
+ 1
24
Add tool

Amazon SQS vs Apache Pulsar: What are the differences?

Introduction

This Markdown document provides a comparison between Amazon Simple Queue Service (SQS) and Apache Pulsar, highlighting the key differences between the two messaging services.

  1. Scalability: Amazon SQS is highly scalable and can handle a large number of messages per second, making it suitable for applications with high throughputs. On the other hand, Apache Pulsar offers topic-level scalability, allowing individual topics to handle high message rates independent of other topics in the system.

  2. Latency: Amazon SQS generally has higher latency compared to Apache Pulsar. SQS is primarily designed for high durability and availability, sacrificing real-time responsiveness. Pulsar, on the other hand, offers low latency messaging with its distributed architecture and efficient message publication and consumption mechanisms.

  3. Message Ordering: Amazon SQS offers ordered message processing within a single queue, ensuring that messages are delivered and processed in the order in which they were sent. In Apache Pulsar, message ordering is maintained within a single partition or topic, but not across multiple partitions or topics by default.

  4. Event Time: Exactly Once Semantics: In Amazon SQS, the exactly-once processing of messages is not provided out of the box. It offers at-least-once message delivery, and deduplication mechanisms need to be implemented by the application developer. Apache Pulsar, on the other hand, provides built-in support for exactly-once semantics using event time in its log-based architecture.

  5. Multi-tenancy: Amazon SQS is designed to be a fully isolated service with per-queue resource allocation, offering dedicated resources for each queue. In contrast, Apache Pulsar supports multi-tenancy by allowing multiple topics or namespaces to share the same cluster resources while maintaining data isolation.

  6. Message Retention: Amazon SQS retains messages for a configurable period, but there is no built-in message retention mechanism beyond the configured retention period. Apache Pulsar provides configurable message retention policies at both the topic and cluster level, allowing message expiration and automatic cleanup based on time or size.

In Summary, Amazon SQS and Apache Pulsar have key differences in scalability, latency, message ordering, event time processing, multi-tenancy, and message retention. Each messaging service offers distinct features and trade-offs, allowing developers to choose the most suitable technology for their specific use cases.

Advice on Amazon SQS and Apache Pulsar
MITHIRIDI PRASANTH
Software Engineer at LightMetrics · | 4 upvotes · 268.8K views
Needs advice
on
Amazon MQAmazon MQ
and
Amazon SQSAmazon SQS
in

I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

See more
Replies (1)
Andres Paredes
Lead Senior Software Engineer at InTouch Technology · | 1 upvotes · 205.7K views
Recommends
on
Amazon SQSAmazon SQS

Mithiridi, I believe you are talking about two different things. 1. If you need to process messages with delays of more 15m or at specific times, it's not a good idea to use queues, independently of tool SQM, Rabbit or Amazon MQ. you should considerer another approach using a scheduled job. 2. For dead queues and policy retries RabbitMQ, for example, doesn't support your use case. https://medium.com/@kiennguyen88/rabbitmq-delay-retry-schedule-with-dead-letter-exchange-31fb25a440fc I'm not sure if that is possible SNS/SQS support, they have a maximum delay for delivery (maxDelayTarget) in seconds but it's not clear the number. You can check this out: https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Amazon SQS
Pros of Apache Pulsar
  • 62
    Easy to use, reliable
  • 40
    Low cost
  • 28
    Simple
  • 14
    Doesn't need to maintain it
  • 8
    It is Serverless
  • 4
    Has a max message size (currently 256K)
  • 3
    Triggers Lambda
  • 3
    Easy to configure with Terraform
  • 3
    Delayed delivery upto 15 mins only
  • 3
    Delayed delivery upto 12 hours
  • 1
    JMS compliant
  • 1
    Support for retry and dead letter queue
  • 1
    D
  • 7
    Simple
  • 4
    Scalable
  • 3
    High-throughput
  • 2
    Geo-replication
  • 2
    Multi-tenancy
  • 1
    Pulsar Functions
  • 1
    Secure
  • 1
    Stream SQL
  • 1
    Horizontally scaleable
  • 1
    Easy to deploy
  • 1
    Fast

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon SQS
Cons of Apache Pulsar
  • 2
    Has a max message size (currently 256K)
  • 2
    Proprietary
  • 2
    Difficult to configure
  • 1
    Has a maximum 15 minutes of delayed messages only
  • 1
    Very few commercial vendors for support
  • 1
    LImited Language support(6)
  • 1
    No one and only one delivery
  • 1
    No guaranteed dliefvery
  • 1
    Not jms compliant
  • 1
    Only Supports Topics

Sign up to add or upvote consMake informed product decisions

What is Amazon SQS?

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

What is Apache Pulsar?

Apache Pulsar is a distributed messaging solution developed and released to open source at Yahoo. Pulsar supports both pub-sub messaging and queuing in a platform designed for performance, scalability, and ease of development and operation.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Amazon SQS?
What companies use Apache Pulsar?
See which teams inside your own company are using Amazon SQS or Apache Pulsar.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Amazon SQS?
What tools integrate with Apache Pulsar?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Amazon S3KafkaZookeeper+5
8
1559
GitHubPythonNode.js+47
54
72280
GitHubGitSlack+30
27
18273
GitHubDockerAmazon EC2+23
12
6560
GitHubPythonSlack+25
7
3148
What are some alternatives to Amazon SQS and Apache Pulsar?
Amazon MQ
Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud.
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
Redis
Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
ActiveMQ
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
Amazon SNS
Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint.
See all alternatives