How LiveSync works
LiveSync is a powerful realtime data synchronization product designed to facilitate broadcasting realtime updates from backend databases to application clients at scale. LiveSync ensures that data updates are propagated reliably, and in order, to all connected clients in realtime.
LiveSync can be used in applications where your database is the source of truth for the application state, and that state needs to be reflected in realtime to client applications. LiveSync enables this data synchronisation while maintaining data integrity and low latency.
By using Ably Pub/Sub channels and SDKs, clients subscribing to messages published by a LiveSync database connector benefit from features like connection-recovery, exactly-once delivery and ordering guarantees out of the box. Ably’s platform guarantees and four pillars of dependability apply by default.
Channel-based broadcasting
Ably’s pub/sub channels are the mechanism used by LiveSync for synchronizing data updates across clients. When a message is published on a channel by the database connector, it is immediately broadcast to all subscribers of that channel.
Hosted database connectors
Take advantage of the Ably hosted database connectors to automatically publish changes from your database as messages on Ably channels. The hosted database connectors support controlling which events are routed to which channels, and using Ably’s Auth and Capabilities you can control which channels a client is allowed to access.
Ably provides hosted connectors for:
Use cases
LiveSync can benefit a wide range of applications where it’s important to broadcast database changes in realtime to keep clients in sync, including: Customer Relationship Management (CRM) applications, customer support applications, productivity or task management applications, online auctions, collaborative form editing, e-commerce systems, chat conversations, multiplayer turn-based games and realtime newsfeeds.
Pricing
LiveSync pricing is mainly based on message consumption (alongside concurrent connections and concurrent channels). This means that each update published from the database connector to Ably channels is counted as a single message. The message is received by every client subscribed to that channel, each of which counts as one additional message. If, for example, one update is published by the database connector and there are three clients subscribed, that one update will lead result in four messages in total.
Development status
LiveSync is in public beta so that you can explore its capabilities. Your feedback will help prioritize improvements and fixes for subsequent releases.