More comparisons

Amazon API Gateway vs deepstream.io

This Amazon API Gateway 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.

Easily build complete, trusted realtime functionality.

Take our APIs for a spin

Amazon API Gateway

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.33 / 5

Getting started guides / 5

Information architecture and developer journey / 5

API reference documentation / 5

Readability, design and navigation / 5

Quality of code / 5

Breadth and quality of tutorials / 5

“The Amazon API Gateway documentation is broadly partitioned into getting started guides, tutorials, service features, references, and misc info, such as FAQs. The information architecture and navigation experience are mostly good. However, the developer journey is not straightforward since API Gateway works with other AWS services, such as IAM and AWS Lambda. You need to look at the respective products' documentation to understand how they work together with the API Gateway. The documentation provides tutorials for most API Gateway features, but the code examples are limited to Node.js and Python.”

4 / 5

Getting started guides / 5

Information architecture and developer journey / 5

API reference documentation / 5

Readability, design and navigation / 5

Quality of code / 5

Breadth and quality of tutorials / 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
4.33 / 5

Ease of use / 5

Stats and reports / 5

Functionality / 5

“The Amazon API Gateway console is easy to use, but only once you know your way around it. More tooltips and contextual help would have been great. The console provides ways of creating APIs and integrating them with backend services.  It also provides different metrics, such as the number of API calls and errors or latency-related stats. The console has all required core functionality for API configuration options such as updating, deleting, deploying, or integrating them with various services. The interface could do with a refresh, as the design is by no means visually appealing.”

4 / 5

Ease of use / 5

Stats and reports / 5

Functionality / 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

8 AWS SDKs to use the Amazon API Gateway service

Including:

  • JavaScript

  • Java

  • PHP

Note that when you create REST APIs with Amazon API Gateway, you can also generate client SDKs, enabling clients to call your REST APIs in a platform or language-specific way (e.g., JavaScript, Android, iOS).

3 SDKs

Including:

  • JavaScript 

  • Java

  • Android

API structure

Reviewed by 3+ independent developers

4.25 / 5

API consistency across SDKs / 5

Well structured / 5

Intuitive / 5

Simple / 5

“The Amazon API Gateway service APIs are part of the standard AWS SDKs. The API Gateway docs provide separate reference pages for each programming language. The APIs are largely consistent, barring some language-specific constructs. Once you learn your way around the console and go through the API reference, the APIs are pretty easy to use.”

3 / 5

API consistency across SDKs / 5

Well structured / 5

Intuitive / 5

Simple / 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 API Gateway

deepstream.io

"Hello world" code example
// Note: The code below demonstrates how AWS API Gateway works with AWS Lambda

// AWS APIGateway configuration required to handle AWS Lambda service

'use strict';
console.log('Loading hello world function');
 
exports.handler = async (event) => {
    let name = "you";
    let city = 'World';
    let time = 'day';
    let day = '';
    let responseCode = 200;
    console.log("request: " + JSON.stringify(event));
    
    if (event.queryStringParameters && event.queryStringParameters.name) {
        console.log("Received name: " + event.queryStringParameters.name);
        name = event.queryStringParameters.name;
    }
    
    if (event.queryStringParameters && event.queryStringParameters.city) {
        console.log("Received city: " + event.queryStringParameters.city);
        city = event.queryStringParameters.city;
    }
    
    if (event.headers && event.headers['day']) {
        console.log("Received day: " + event.headers.day);
        day = event.headers.day;
    }
    
    if (event.body) {
        let body = JSON.parse(event.body)
        if (body.time) 
            time = body.time;
    }
 
    let greeting = `Good ${time}, ${name} of ${city}.`;
    if (day) greeting += ` Happy ${day}!`;

    let responseBody = {
        message: greeting,
        input: event
    };
    
    // The output from a Lambda proxy integration must be 
    // in the following JSON object. The 'headers' property 
    // is for custom response headers in addition to standard 
    // ones. The 'body' property  must be a JSON string. For 
    // base64-encoded payload, you must also set the 'isBase64Encoded'
    // property to 'true'.
    let response = {
        statusCode: responseCode,
        headers: {
            "x-custom-header" : "my custom header value"
        },
        body: JSON.stringify(responseBody)
    };
    console.log("response: " + JSON.stringify(response))
    return response;
};
// 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 API Gateway

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 API Gateway 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 API Gateway 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

Throughput

10.000 requests per second (default quota)

Maximum message size

128 KB for WebSocket APIs

10 MB for REST APIs

Maximum number of channels

N/A

Maximum number of concurrent connections

Amazon API Gateway doesn't enforce a quota on concurrent connections. The maximum number of concurrent connections is determined by the rate of new connections per second and a maximum connection duration of two hours.

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 API Gateway 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 API Gateway 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 API Gateway and deepstream.io support?

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

Cloud models

Which popular cloud models do Amazon API Gateway 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.95%

No specific uptime SLA

Quality of Service

What QoS guarantees do Amazon API Gateway 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 API Gateway 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 API Gateway 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 API Gateway 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 API Gateway 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
  • EU GDPR
  • SOC 2 TYPE I
  • SOC 2 Type II
  • HIPAA
  • EU GDPR
Pricing & Support

Free package

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

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

The Amazon API Gateway free package includes one million API calls received for REST APIs, one million API calls for HTTP APIs, one million messages, and 750,000 connection minutes for WebSocket APIs per month for up to 12 months. Beyond the 12 months, there is no free package.

N/A

Pricing model

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

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

Amazon API Gateway pricing is usage-based and calculated per month.

HTTP APIs

You pay for the number of API calls per month:

- $1 per million calls for the first 300 million. 

- For 300+ million calls, the price is $0.90 per million.

REST APIs

You pay for the number of requests per month:

- $3.50 per million calls for the first 333 million requests. 

- For the next 667 million requests, the price is $2.80 per million.

You can optionally provision dedicated caching for REST APIs, which is also charged. For example, the price for a cache memory size of 237 GB is $3.80 per hour.

WebSocket APIs

You pay for message transfer (requests) and connection minutes:

- $1 per million requests per month (for the first 1 billion. If you exceed 1 billion requests, the pricing is $0.80 per million). 

- $0.25 per million connection minutes. 

Note that we have used US East (Ohio) as a reference point, but the pricing values differ across regions.

You may also incur additional charges for external data transfers or if you use Amazon API Gateway in conjunction with other AWS services (such as AWS Lambda).

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 API Gateway and deepstream.io enterprise packages offer?

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

There is no Amazon API Gateway-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
4.50 / 5

Presence on multiple channels / 5

Size and activity / 5

“Among the AWS ecosystem, Amazon API Gateway seems to be one of the most popular products, which makes sense since it allows you to build your very own APIs. There are many GitHub repos created by the community, some of which have hundreds of stars. There are over 5000 questions on Stack Overflow under the aws-api-gateway tag, some of which have hundreds of thousands of views. It’s a big, active, and interested community.”

5 / 5

Presence on multiple channels / 5

Size and activity / 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 API Gateway 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 API Gateway was last updated on 10 October 2024 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.


View more comparisons