- Ably FAQs
- Performance and Redundancy
- Performance
-
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
-
Integrations
-
Migrating to Ably from an existing service
Do you have any single point of congestion that limits your global performance?
No, the Ably service, running in over 16+ data centres and 175+ edge acceleration points-of-presence globally, provides a true mesh distributed system ensuring that there is both no single point of congestion and no single point of failure. Ably is designed to always route messages using the least number of network hops minimising latency and ensuring maximum performance for clients no matter their location.
The details below explain how Ably solves the challenge of efficient global routing at all times:
- A publish only server located in New York is routed to the nearest data centre (US East) using our latency based routing; Msg A published to US East is routed directly to clients in US East, and once to every other data centre with clients subscribed for messages; Clients in all other regions subscribed for messages receive Msg A directly from the data centre they are connected to
- A Publish & subscribe client in London is routed to the nearest data (EU West) using our latency based routing; Msg B published to EU West is routed directly to clients in EU West, and once to every other data centre with clients subscribed for messages; Clients in all other regions subscribed for messages receive Msg B directly from the data centre they are connected to