- Ably FAQs
- Ably architecture, transports, and security
- Protocol support and protocol adapters
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Reactor Queues, Events and Firehose
-
Migrating to Ably from an existing service
-
Connections
Do you support the PubNub protocol?
Yes, we have a PubNub protocol adaptor that allows customers who are migrating from PubNub to use the PubNub client libraries directly with our service. PubNub protocol support is provided as part of the Ably Protocol Adapter service.
Find out how to start using the Ably PubNub protocol adaptor »
For example, a typical migration from PubNub to Ably goes as follows:
- Initially a customer will simply change the host name for all of their PubNub client library integrations to use our endpoints.
- A customer will then migrate one app at a time over to our Ably client libraries that provides access to all of our features. At this stage, some of the customer's apps will be using PubNub client libraries and others will be using Ably's client libraries. However, as we are translating the PubNub protocol, there is no interruption and interoperability between both protocols is provided by Ably.
- Customer will finally migrate all their apps and servers to use the Ably client libraries and will terminate their old contracts.
If you are interested in migrating from PubNub and want to use our protocol adaptors, please read our FAQ on how to start using the Ably PubNub protocol adaptor.
Alternatively, you can find our more about Ably's protocol agnostic approach, our protocol adaptors and how they work.