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.