|Why it matters?|
|Transparent usage based pricing||
Ably's pricing is transparent. You pay for the messages, peak active channels and peak connections you use for the month. You can either pay for what you've used at the end of the month, or reserve capacity in advance each month and benefit from a discount.
deepstreamHub packages are priced in tiers meaning that if you were on their 2k connection package at $80 per month, and you needed to grow 3k connections, you would have to upgrade to the next tier at $160 per month (2x the price). At Ably, you’d just pay for an additional 1k connections for $12.50.See Ably's pricing calculator
Example pricing comparison:
||$62.99 per month||$160 per month||
Our flexible packages ensure we deliver value to our customers who pay for what they use. deepstreamHub’s package for up to 5k connections starts at $160 and thus only delivers value if you use exactly 5k connections and all 120m messages per month.See how much you can save
|Pricing that incentivizes you to grow||
Our cost per message and connection goes down as you use more - customers benefit from the economies of scale and paying for what they use.
deepstreamHub offer packages in tiers which means if you exceed the connections for that tier, you would probably upgrade to the more expensive tier and not benefit from economies of scale.Estimate how much you'll pay once you grow
|Global datacenters locations||16||1||
Ably have 16 datacenters globally. We can ensure that your users always experience the lowest possible latency by connecting to the closest datacenter, and have complete availability by connecting to alternative healthy datacenters when necessary.
deepstreamHub clusters must exist in a single data centre region.Find out more about Ably's datacenters
|Latency based routing||
Our latency based routing ensures that users anywhere in the world connect through one of our 180 edge acceleration PoPs to one of our 16 Ably datacenters. deepstreamHub do not offer this as all traffic is directed to a single datacenter location.Find out more about Ably's latency based DNS
|Binary encoded messages||
Encoding messages in binary format is faster. It reduces bandwidth to send and receive messages, and streamlines the processing time for clients and servers when encoding and decoding messages.
Ably and deepstreamHub both support the use of binary data.Find out more about our binary protocol
|Redundancy and Reliability|
|Mesh architecture / no central point of failure / self-healing cluster||Partial||
The Ably platform is designed with no single point of failure and to be self-healing. All our customers benefit from their apps running on all of our datacenters providing resilience, reliability and low latencies globally.
deepstreamHub stores data across a combination of storage and cache layers. This allows the individual servers to go down / fail over without causing any data-loss, as the data is distributed across multiple nodes. However, as the deepstreamHub platform relies on shared services such as a Redis for a message bus, that layer itself becomes a point of failure and congestion.Find out more about Ably's mesh architecture
Ably's servers are located in 16 datacenters covering 4 continents with each datacenter designed to operate as part of the global cluster when available, but operate autonomously when necessary.
deepstreamHub do not operate with multiple datacenters.Find out where Ably's servers are located
|Data replicated in multiple regions||Partial||
Ably stores every message in at least two datacenters and separate geographical regions. This ensures that an outage in any datacenter or region cannot result in data loss.
deepstreamHub do not operation with multiple datacenters and, as such, data is typically stored in the location the platform is running in. It is possible however for a data layer to be used that could be replicated such as Mongo with replication across regions or datacenters.Find out about Ably's QoS and message delivery guarantee
|QoS & message delivery guarantee||Unknown||
Ably provides guaranteed message delivery and continuity across disconnections. Publishers only receive an ACK when data is persisted in two locations, and subscribers never lose data during brief disconnections as we maintain connection state for each client on our servers.
We are not clear on what QoS promises the platform can offer given the different plugins for different protocols and backends could significantly change the quality of service available in the design.Find out about Ably's message delivery guarantee
|100% uptime guarantee||On demand||
deepstreamHub only offer SLAs for their personalised enterprise customers.Find out about Ably's 100% uptime guarantee
|Message and worker queues||
Data published into Ably's realtime system can be moved into traditional message queues for realtime or batch processing.
deepstreamHub does not offer message queuing features or a means to distribute data using once-only pattern to your server workers.Find out more about our Reactor Queues
WebHooks provide a means to get messages, channel lifecycle and present events pushed to your servers over HTTP.
deepstreamHub use WebHooks as a form of authentication but not as a means to get messages, channel lifecycle and present events such as Ably.Find out more about WebHooks
|Serverless cloud function invocation||
Ably can trigger serverless functions on any third platforms such as Amazon Lambda, Microsoft Azure or Google Function.
deepstreamHub currently do not offer the ability to use serverless functions.Find out more about Reactor Functions
Presence allows you to subscribe to events when users or devices enter or leave channels. This is a useful feature for collaborative apps, games and chat rooms.
Both Ably and deepstreamHub provide presence capabilities yet only Ably emits presence events when a present member has updated their member data.Find out more about Presence
Ably's message history feature provides a means for clients or servers to retrieve messages that were previously published on a channel.
deepstreamHub offers message history through its persistence layer.Find out more about our History API
|Realtime data firehose||Partial||
Stream your realtime data published within the Ably platform directly to another streaming or queueing service such as Amazon Kinesis, Apache Storm or Kafka.
The deepstreamHub community has built a number of plugins that offer similar capabilities. However, given each plugin is built by the community, it is not clear how these features are offered consistently across different target platforms.Find out more about our Reactor Firehose
|Reliable message ordering||Unlikely||
Ably ensures that messages are delivered to persistently connected subscribers in the order they were published on each channel.
It is not clear how deepstreamHub provides guaranteed ordering of messages given the messaging backends they rely on, such as Redis, do not generically provide that functionality.Find out more about reliable ordering
Ably offers push notifications, with smart notifications coming soon.
deepstreamHub’s push notifications are still in their feature backlog.Find out more about Push Notifications
|Custom domain endpoint (CNAME)||
Ably supports custom domains for our Enterprise customers allowing them to connect to Ably using a CNAME such as "realtime.your-company.com".
deepstreamHub does not provide support for custom CNAME endpoints.Find out more about our custom domains
|Client libraries and protocol support|
|Native client libraries for every popular platform||
Ably offer a considerable range of client library SDKs for every popular platform.View our client library SDKs
|Ably protocol support||
Ably's realtime protocol provides an efficient means to reliably and efficiently publish and subscribe to realtime data.
deepstreamHub has its own realtime protocols.See which libraries natively support the Ably protocol
|Competitor protocol support||
The Ably platform is designed to be protocol-agnostic and ensure protocol interoperability. Ably supports the deepstreamHub's protocol.
deepstreamHub does not currently support competitor realtime platform protocols.Find out which protocols we support
The Ably platform is designed to be protocol-agnostic and ensure protocol interoperability. Ably supports MQTT./p>
deepstreamHub only supports MQTT on their enterprise product.Find out which protocols we support
|SSE protocol support||
The Ably platform is designed to be protocol-agnostic and ensure protocol interoperability. That's why we support SSE. deepstreamHub doesn't support SSE.Find out which protocols we support
Using our protocol adapters, our customers can use the large selection of PubNub embedded client libraries for low energy and other embedded devices.
deepstreamHub has a very limited set of client libraries suitable for embedded devices.See the list of supported embedded libraries
|White-label browser library||
deepstreamHub does not, as far as we are aware, offer white-label libraries.Find out about our white-label libraries
|Continuity and connection state recovery||Possible||
Ably provides continuity for clients that become disconnected for reasons such as going through a tunnel or changing networks. Ably stores the connection state for each client on its servers so that clients that reconnect within two minutes can resume their connection and receive all messages published whilst they were disconnected.
It is not clear if deepstreamHub provides connection state recovery. Given connections can be resumed and data synchronization can be completed, it is quite possible an equivalent is available.Find out more about connection state recovery
|1st class WebSocket support||
WebSockets are widely regarded as the most efficient HTTP compatible transport for full duplex realtime communication between devices.View our supported transports
|Fallback to Comet (XHR) and Long Polling for older browsers||
Whilst most modern devices support WebSockets, there are situations where the device or the network environment requires use of HTTP transports.View our supported transports
Ably and deepstreamHub offer TLS connections ensuring that all data in transit is encrypted.Find out more about SSL/TLS
|Token based authentication||
Token based authentication ensures your private key is never shared and instead a short-lived token is used to authenticate.
Ably allows configurable policies and an identity to be embedded in a token ensuring you have complete control over what actions your users can perform such as limiting which channels they can subscribe or publish to.
deepstreamHub also provide a Token based authentication service.Find out more about Ably's authentication
|JSON Web Tokens support||
Using JWT allows for easy integration with your existing authentication systems, along with ensuring your private key is never shared.
Ably allows for not only Ably Tokens to be embedded within JWTs, but also for JWTs to be signed by Ably API keys and used themselves for authentication.
deepstreamHub also supports JWT.Find out more about using JWT with Ably
|Configurable private key permissions||
Ably provides support for private API keys with configurable permissions including restrictions on channels or operations.
deepstreamHub does not support configurable permission for keys.Find out more about API keys
|Configurable channel permissions||
Ably provides channel rules providing you with the flexibility to maintain control of your channels, such as requiring SSL/TLS or only identified authenticated clients on a channel.
deepstreamHub does not support configurable channel permissions.Find out more about channel rules
|Encrypted message payloads||
Ably's AES encryption allows messages to be encrypted using the provided private key before they are published to Ably. As a result, messages are practically impossible intercept and view for anyone including Ably. For very sensitive data, this ensures you can safely use us knowing your payloads are always secure and opaque.
deepstreamHub does not provide payload encryption in their client libraries.Find out more about Ably's encryption
* deepstreamHub ceased trading in December 2017. All information regarding deepstreamHub was obtained on or before November 2017. It is therefore possible that some of this information may now be out of date. If you believe that any of this information is incorrect, please get in touch with us so that we can correct it immediately.