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

Amazon SQS

2K
1.8K
+ 1
166
ejabberd

30
40
+ 1
0
Add tool

Amazon SQS vs ejabberd: What are the differences?

Amazon SQS: Fully managed message queuing service. 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; ejabberd: A scalable and robust instant messaging server. It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.

Amazon SQS and ejabberd belong to "Message Queue" category of the tech stack.

Some of the features offered by Amazon SQS are:

  • A queue can be created in any region.
  • The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.
  • Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.

On the other hand, ejabberd provides the following key features:

  • Cross-platform
  • Administrator-friendly
  • Internationalized

ejabberd is an open source tool with 4.18K GitHub stars and 1.25K GitHub forks. Here's a link to ejabberd's open source repository on GitHub.

Medium, Lyft, and Coursera are some of the popular companies that use Amazon SQS, whereas ejabberd is used by AppScale Systems, KongHack Inc., and UrbanClap. Amazon SQS has a broader approval, being mentioned in 497 company stacks & 402 developers stacks; compared to ejabberd, which is listed in 5 company stacks and 3 developer stacks.

Advice on Amazon SQS and ejabberd
MITHIRIDI PRASANTH
Software Engineer at LightMetrics · | 4 upvotes · 159.3K views
Needs advice
on
Amazon SQSAmazon SQS
and
Amazon MQAmazon MQ
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 · 126.2K views
Recommends
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 ejabberd
  • 60
    Easy to use, reliable
  • 39
    Low cost
  • 27
    Simple
  • 13
    Doesn't need to maintain it
  • 8
    It is Serverless
  • 4
    Has a max message size (currently 256K)
  • 3
    Easy to configure with Terraform
  • 3
    Triggers Lambda
  • 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
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Amazon SQS
    Cons of ejabberd
    • 2
      Has a max message size (currently 256K)
    • 2
      Proprietary
    • 2
      Difficult to configure
    • 1
      Has a maximum 15 minutes of delayed messages only
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      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 ejabberd?

      It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.

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

      What companies use Amazon SQS?
      What companies use ejabberd?
      See which teams inside your own company are using Amazon SQS or ejabberd.
      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 ejabberd?

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

      Blog Posts

      GitHubPythonNode.js+47
      53
      70441
      GitHubGitSlack+30
      26
      16540
      GitHubDockerAmazon EC2+23
      12
      6402
      GitHubPythonSlack+25
      7
      2951
      What are some alternatives to Amazon SQS and ejabberd?
      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