More comparisons

Amazon SQS vs deepstream.io

This Amazon SQS vs deepstream.io comparison was created based on reviews from developers and our best attempts to perform analysis by looking at documentation and other publicly available resources.

Need help choosing a realtime messaging solution?

Contact us

Amazon SQS

deepstream.io

Getting started and developer experience

Time to "hello world"

Reviewed by 3+ independent developers

Ratings were given based on the average amount of time it takes to sign up to a new account and publish the first message.

4 / 5

5 = <30 min
4 = 30 min - 1 h
3 = 1-2 h
2 = 2-4 h
1 = 4+ h

View code example
4 / 5

5 = <30 min
4 = 30 min - 1 h
3 = 1-2 h
2 = 2-4 h
1 = 4+ h

View code example

Demos / Tutorials

A selection of online demos and tutorials so you can test and see the code in action.

Explore Ably's tutorials for our pub/sub messaging platform

Documentation

Reviewed by 3+ independent developers

Explore Ably's documentation for our pub/sub messaging platform
4 / 5

Getting started guides4 / 5

Information architecture and developer journey4 / 5

API reference documentation4 / 5

Readability, design and navigation5 / 5

Quality of code5 / 5

Breadth and quality of tutorials2 / 5

“The information architecture is largely intuitive and helpful, which makes it easy to navigate through docs. From a content perspective, the documentation is good - instructions are generally clear and don’t leave room for interpretation. The getting started guide is easy to follow - if anything, the process is a bit tedious due to the number of steps involved. The code samples are good throughout. Official docs don’t contain a lot of tutorials - there’s barely any. It would have been good to see (more) use case-focused tutorials and demos. You can easily forget about the API reference, which is only listed on the docs homepage, but it’s not referenced in the developer guide at all.”

4 / 5

Getting started guides4 / 5

Information architecture and developer journey3 / 5

API reference documentation4 / 5

Readability, design and navigation4 / 5

Quality of code5 / 5

Breadth and quality of tutorials4 / 5

The deepstream.io documentation is nicely written and features several components: GitHub, guides, tutorials, docs, blog, and miscellaneous info, such as FAQs. There’s a Getting Started guide using HTTP API, JavaScript Client API, and Java Client API, with code snippets throughout. The API reference is detailed for each SDK and information architecture is pretty nice. Most sections of the documentation are well cross-linked; however, the navigation experience could be improved, especially around the API reference – some links return 404. Also, some documentation pages need to be revamped. The documentation provides tutorials for most deepstream.io features but unfortunately, there’s no demos. The documentation for the core features (data-sync, records, auth, permissions, events, rpc, etc.) is well written, but could be more detailed.

Dashboard or dev console

Reviewed by 3+ independent developers

Sign up for free and explore Ably's pub/sub messaging platform
5 / 5

Ease of use5 / 5

Stats and reports5 / 5

Functionality5 / 5

“The Amazon SQS console allows you to perform queue-related CRUD operations easily. In addition, for each queue, you can manage various settings, such as Lambda triggers, access policy, or encryption. The console also allows you to monitor various metrics, such as the size of messages added to a queue or the number of messages available for retrieval from a queue. The functionality is intuitive, and the dev console is pretty easy to use once you learn your way around it a bit. As a minus, the UI, while simple, is quite boring and dry”.

4 / 5

Ease of use3 / 5

Stats and reports4 / 5

Functionality5 / 5

The deepstream.io dashboard might be a bit overwhelming to use or understand without documentation. The dashboard allows you to explore realtime data, configure permission, as well as view important metrics over time such as total messages used, active connections, cluster size, and CPU usage.

The UI design is a bit outdated and could perhaps benefit from a revamp.

SDKs

Note: Only official SDKs were taken into account.

Explore Ably's 25+ SDKs for our pub/sub messaging platform

9 SDKs

Including:

  • Ruby

  • .NET

  • JavaScript

3 SDKs

Including:

  • JavaScript 

  • Java

  • Android

API structure

Reviewed by 3+ independent developers

4 / 5

API consistency across SDKs4 / 5

Well structured4 / 5

Intuitive4 / 5

Simple4 / 5

“The Amazon SQS APIs are well described, intuitively named, and overall easy to understand. The API structure is decently consistent and simple across all SDKs. The API reference is well put together and helps you understand all the various operations and actions you can perform.”

3 / 5

API consistency across SDKs3 / 5

Well structured4 / 5

Intuitive2 / 5

Simple3 / 5

deepstream.io tries to keep its APIs as consistent as possible across SDKs on the client side. However, the APIs are quite complex and counter-intuitive – too many methods make it not straightforward to perform operations in the same order. There’s a separate reference page for each API, which is not great. Developers need to take their time to go through the API reference to be able to use them properly. Documentation and tutorials are helpful in this regard.

Amazon SQS

deepstream.io

"Hello world" code example
// SENDING A MESSAGE

// Load the AWS SDK for Node.js
var AWS = require('aws-sdk');
// Set the region 
AWS.config.update({region: 'REGION'});

// Create an SQS service object
var sqs = new AWS.SQS({apiVersion: '2012-11-05'});

var params = {
   // Remove DelaySeconds parameter and value for FIFO queues
  DelaySeconds: 10,
  MessageAttributes: {
    "Title": {
      DataType: "String",
      StringValue: "The Whistler"
    },
    "Author": {
      DataType: "String",
      StringValue: "John Grisham"
    },
    "WeeksOn": {
      DataType: "Number",
      StringValue: "6"
    }
  },
  MessageBody: "Information about current NY Times fiction bestseller for week of 12/11/2016.",
  // MessageDeduplicationId: "TheWhistler",  // Required for FIFO queues
  // MessageGroupId: "Group1",  // Required for FIFO queues
  QueueUrl: "SQS_QUEUE_URL"
};

sqs.sendMessage(params, function(err, data) {
  if (err) {
    console.log("Error", err);
  } else {
    console.log("Success", data.MessageId);
  }
});

// RECEIVING A MESSAGE

// Load the AWS SDK for Node.js
var AWS = require('aws-sdk');
// Set the region
AWS.config.update({region: 'REGION'});

// Create an SQS service object
var sqs = new AWS.SQS({apiVersion: '2012-11-05'});

var queueURL = "SQS_QUEUE_URL";

var params = {
 AttributeNames: [
    "SentTimestamp"
 ],
 MaxNumberOfMessages: 10,
 MessageAttributeNames: [
    "All"
 ],
 QueueUrl: queueURL,
 VisibilityTimeout: 20,
 WaitTimeSeconds: 0
};

sqs.receiveMessage(params, function(err, data) {
  if (err) {
    console.log("Receive Error", err);
  } else if (data.Messages) {
    var deleteParams = {
      QueueUrl: queueURL,
      ReceiptHandle: data.Messages[0].ReceiptHandle
    };
    sqs.deleteMessage(deleteParams, function(err, data) {
      if (err) {
        console.log("Delete Error", err);
      } else {
        console.log("Message Deleted", data);
      }
    });
  }
});
// Client A
function eventCallback (data) {
    //callback for incoming events 
}

//Subscribing to an event 
client.event.subscribe ('news/sports' , eventCallback)

//Removing specific callback to the event
client.event.unsubscribe ('news/sports' , eventCallback)

//Removing all subscriptions to the event
client.event.unsubscribe ('news/sports')

// Client B
client.event.emit ('news/sports' , 'football is happening' )

// Client B
client.event.listen ('^news /.*' , (match, response) => {
    console.log(match) // 'news/sports'
    if (/* if you want to provide */) { 
        // start publishing data via ` client.event.emit(eventName, /* data */)`
        response.accept()

        response.onStop(() => {
            // stop publishing data
        }) 
    } else {
        response.reject() // let deepstream ask another provider
    }
})

Amazon SQS

deepstream.io

Realtime features

Pub/Sub messaging

Pub/Sub is a design pattern that lets any number of publishers (producers) push messages to channels (also known as topics). Multiple subscribers (consumers) can subscribe to a channel to consume published messages.

Explore Ably's pub/sub messaging implementation

Message queues

A message queue is a form of asynchronous service-to-service communication. Messages are stored on a queue until they are processed. Note that each message is only consumed by one subscriber (consumer).

Explore Ably's message queues implementation

Presence

Presence enables you to track the online and offline status of devices and end-users in real time and to store their state. Essential for chat apps and multiplayer games.

Explore Ably's presence implementation

Message history

Message history provides a means to retrieve previously published messages. For this to be possible, message data must be stored (persisted) somewhere.

Explore Ably's message history implementation

Connection state recovery (stream resume)

In the case of unreliable network conditions, clients may suddenly disconnect.Connection state recovery ensures that when they reconnect, the data stream resumes exactly where it left off.

Explore Ably' s connection state recovery implementation

Guaranteed message ordering

Ordering ensures that messages are delivered to consumers in the same order that producers publish them.

Explore Ably' s guaranteed message ordering implementation

Exactly-once semantics

Exactly-once is a system-wide data integrity guarantee that ensures each message is delivered to consumers exactly-once.

Explore Ably' s idempotent publishing implementation

Message delta compression

Message delta compression enables you to only send the changes from the previous message to subscribers each time there’s an update, instead of the entire message. Useful for use cases where there is a significant degree of similarity between successive messages.

Explore Ably' s message delta compression implementation

Native push notifications

Native push notifications can be used to deliver messages even when clients are offline. Useful for geolocation updates or news alerts.

Explore Ably's push notifications implementation

Webhooks

Webhooks provide a mechanism to get messages and other types of events (such as clients entering or leaving channels) pushed to your servers over HTTP.

Explore Ably's webhooks implementation

Limited

deepstream.io only uses webhooks for user authentication.

Serverless functions

A serverless function is essentially an isolated, single-purpose piece of code that is only executed when it’ triggered by an event. For example, you can use serverless functions to send a welcome message to clients when they become present on chat channels.

Note that serverless functions are usually fully managed by cloud vendors.

Explore Ably's serverless functions implementation

Limited

Can only trigger AWS Lambda functions. Amazon SQS doesn’t have in-built support for other serverless platforms, such as Azure Functions or Google Cloud Functions. 

Built-in integrations

Which popular services & systems are Amazon SQS and deepstream.io integrated with?

Explore Ably's library of integrations

Webhooks

  • Custom
  • IFTTT
  • Zapier

Serverless functions

  • AWS Lambda
  • Cloudflare Workers
  • Google Cloud Functions
  • Microsoft Azure Functions

Streaming

  • Apache Kafka
  • Apache Pulsar
  • Amazon Kinesis
  • Amazon SQS
  • RabbitMQ
  • AMQP

Webhooks

  • Custom
  • IFTTT
  • Zapier

Serverless functions

  • AWS Lambda
  • Cloudflare Workers
  • Google Cloud Functions
  • Microsoft Azure Functions

Streaming

  • Apache Kafka
  • Apache Pulsar
  • Amazon Kinesis
  • Amazon SQS
  • RabbitMQ
  • AMQP

Known limits and constraints

Find out practical limits, such as the maximum message size, or the maximum number of concurrent connections.

Explore the practical limits of the Ably pub/sub messaging platform

Message throughput 

- Standard queues: nearly unlimited  number of API calls per second per API action 

- FIFO queues: 300 API calls per second per API method (3000 transactions per second if you use batching).

Maximum message size

256 KB

Maximum number of queues

Unlimited

Maximum number of connections

By default, a single SQS client has a connection limit of 50 connections. When more than 50 connections are used, the endpoint connections will get queued up, and performance might decrease.

Publisher throughput 

160.000-200.000 updates per second for Single Node

4,000,000,000 messages per hour for Cluster

Maximum message size

1MB 

Maximum number of topics

Unknown

Maximum number of connections

250 for Single Node

750 for Cluster

Supported development platforms, languages, open protocols and cloud models

Development platforms & operating systems

Which popular development platforms and operating systems do Amazon SQS and deepstream.io support via official SDKs?

Explore the development platforms supported by Ably
  • Android
  • Java / JVM
  • iOS
  • macOS
  • iPadOS
  • tvOS
  • watchOS
  • Mono
  • .NET
  • Android
  • Java / JVM
  • iOS
  • macOS
  • iPadOS
  • tvOS
  • watchOS
  • Mono
  • .NET

Languages

Which popular programming languages do Amazon SQS and deepstream.io support via offical SDKs?

Explore the programming languages supported by Ably
  • JavaScript
  • Node.js
  • TypeScript
  • Java
  • Objective-C
  • Swift
  • Go
  • PHP
  • Python
  • Ruby
  • Flutter
  • Clojure
  • Scala
  • JavaScript
  • Node.js
  • TypeScript
  • Java
  • Objective-C
  • Swift
  • Go
  • PHP
  • Python
  • Ruby
  • Flutter
  • Clojure
  • Scala

Open protocols

Which popular open protocols do Amazon SQS and deepstream.io support?

Explore the open protocols supported by Ably
  • WebSocket
  • HTTP / REST
  • AMQP
  • MQTT
  • STOMP
  • SSE
  • Webhooks
  • WebSocket
  • HTTP / REST
  • AMQP
  • MQTT
  • STOMP
  • SSE
  • Webhooks

Cloud models

Which popular cloud models do Amazon SQS and deepstream.io support?

  • Self-hosted
  • Cloud-managed
  • Serverless
  • Globally-distributed
  • Self-hosted
  • Cloud-managed
  • Serverless
  • Globally-distributed
Global and reliable edge service

Edge messaging network with latency-based routing

Latency-based routing ensures that clients are always routed to the nearest datacenter and point of presence.

Explore Ably's routing mechanism that mitigates network and DNS issues

Multi-region data replication (message durability)

Multi-region data replication (storage) protects against single points of failure and ensures message data durability.

Learn how Ably ensures message durability

Limited

deepstream.io stores data in a combination of storage and cache layers for distribution across multiple nodes. However this platform also relies on shared devices such as a Redis for a message bus which itself (Redis layer) might become a point of failure and congestion.

Uptime SLAs

Here’s what the most common SLAs amount to in terms of downtime over a calendar year:

99.999% SLA = 5m 15s downtime per year

99.99% SLA = 52m 35s downtime per year

99.95% SLA = 4h 22m 58s downtime per year

99.9% SLA = 8h 45m 56s downtime per year

99% SLA = 3d 15h 39m 29s downtime per year

Source: https://uptime.is/

99.9%

No specific uptime SLA

Quality of Service

What QoS guarantees do Amazon SQS and deepstream.io provide natively?

Explore Ably's availability and uptime guarantees for our pub/sub messaging platform
  • Multi-region data replication (storage)
  • Exactly-once semantics
  • Guaranteed message ordering
  • Connection state recovery (stream resume)
  • Multi-region data replication (storage)
  • Exactly-once semantics
  • Guaranteed message ordering
  • Connection state recovery (stream resume)
Security

API key authentication

The simplest way to authenticate. Involves using private API keys that you can usually create and edit via a dashboard. Recommended to be used server-side, as private API keys shouldn’t be shared with untrusted parties.

Explore Ably's implementation of API key authentication

Token-based authentication

Which popular token-based authentication mechanisms do Amazon SQS and deepstream.io support?

Note that token-based authentication is usually the recommended strategy on the client-side as it provides more fine-grained access control and limits the risk of credentials being compromised.

Explore Ably's implementation of token-based authentication
  • Ephemeral tokens
  • JWTs
  • Ephemeral tokens
  • JWTs

Configurable rules and permissions

Which types of configurable rules and permissions do Amazon SQS and deepstream.io support?

Explore Ably's configurable rules and permissions
  • API keys rules and permissions
  • Operation rules and permissions
  • Admin rights
  • API keys rules and permissions
  • Operation rules and permissions
  • Admin rights

Message encryption

Which types of message encryption do Amazon SQS and deepstream.io support?

Explore Ably's message encryption mechanisms
  • Encrypted at rest
  • Encrypted in transit
  • Message payload encryption
  • Encrypted at rest
  • Encrypted in transit
  • Message payload encryption

Formal certifications

Which formal certifications are Amazon SQS and deepstream.io compliant with?

Explore Ably's security and compliance for our pub/sub messaging platform
  • SOC 2 TYPE I
  • SOC 2 Type II
  • HIPAA
  • ISO 27001
  • EU GDPR
  • SOC 2 TYPE I
  • SOC 2 Type II
  • HIPAA
  • ISO 27001
  • EU GDPR
Pricing & Support

Free package

What do the free packages offered by Amazon SQS and deepstream.io consist of?

Explore Ably's free package for our pub/sub messaging platform

1 million Amazon SQS requests for free each month.

N/A

Pricing model

How are the Amazon SQS and deepstream.io pricing models calculated?

Explore Ably's pricing model for our pub/sub messaging platform

Beyond the 1 million free Amazon SQS requests each month (which applies to all customers), the monthly cost of requests is calculated as such:

- $0.40 per 1 million requests (Standard Queues)

- $0.50 per 1 million requests (FIFO Queues)

Data transfer out of Amazon SQS is also charged. The first GB / month is free. Pricing varies depending on region and volume of data. For example, in US East (Verizon) - Boston, the price for the next 9.999 TB / month is $0.108 per GB

deepstream.io pricing is usage-based and calculated per hour.

$0.052 per hour for a six-instance cluster on AWS EC2  t2.medium

$0.008 per hour for a single node on cache.t2.medium

It’s unclear how pricing is calculated for the Enterprise package.

Enterprise package

What benefits do the Amazon SQS and deepstream.io enterprise packages offer?

Explore Ably's enterprise package for our pub/sub messaging platform

There is no Amazon SQS - specific enterprise package.

No Enterprise package is explicitly specified. However, it can be obtained by contacting the vendor directly.

Community

Reviewed by 3+ independent developers

Explore Ably's community support channel for our pub/sub messaging platform
3.50 / 5

Presence on multiple channels4 / 5

Size and activity3 / 5

“As we all know, overall, Amazon has a strong and diverse online community that spans various platforms and websites, like Reddit, Stack Overflow, or the AWS forums. With that in mind, the SQS community is not as active or helpful as you’d expect. For example, if you look at the Amazon SQS AWS forum, you will notice there are not that many questions asked over the past year. And while the published questions can get hundreds or even thousands of views, most of them barely have a few replies, if any at all.”  

5 / 5

Presence on multiple channels5 / 5

Size and activity5 / 5

deepstream.io has a strong community presence on various channels, such as Stack Overflow, Slack, GitHub, and Twitter. Their community is active, approachable, and helpful, and generates a lot of content: 110 repositories, 6.8K stars, and 383 forks on GitHub. Similarly, there are over 100 questions on Stack Overflow, 690 users on Slack and more than 1000 followers on Twitter. There are no events, and no community presence on Discourse, and Gitter.

Support

What types of support options and response times do Amazon SQS and deepstream.io offer?

Explore Ably's support options for our pub/sub messaging platform

General support options

Email, support ticket, phone, technical documentation, community support (e.g. forums or Stack Overflow). 

Enterprise support

Amazon offers an enterprise package, which includes 24/7 phone, email, and chat access to Cloud Support Engineers, Infrastructure Event Management support, and a designated technical account manager.

Response time

< 24 hours for general guidance queries

< 1 hour for Production system down incidents (only applies to Business & Enterprise support packages).

General Support Options

Email, technical documentation, community support.

Response time

< 24 hours for non-technical queries

< 1 hour for production system down incident (only applies to Enterprise support package)

Disclaimer: The information presented for Amazon SQS was last updated on 16 October 2020 and on 28 February 2021 for deepstream.io. It is possible that some details may now be out of date. If you think that’s the case, please let us know so we can update them. In any case, you should not rely solely on the information presented here and must check with each provider before deciding to integrate or buy any of these two solutions.