With Space Cloud, you can subscribe to realtime changes in your database.

How it works

Space Cloud allows you to subscribe to a particular result set in your database by specifying a where clause. So whenever anything within that result set changes, i.e. new documents are added/updated/deleted, you get notified.

However, for efficient bandwidth utilization, Space Cloud doesn’t send the entire result set on every change. It only sends the changed document to the concerned clients. The client can choose whether or not to receive the initial documents in the result set at the time of subscribing.

Note: You can write a stateful link if you wish to maintain the entire result set while using any REST or GraphQL client libraries. However, if you are using one of the client SDKs of Space Cloud, you get the stateful link out of the box.


To offload the database, Space Cloud does not rely on any CDC (Change Data Capture) mechanism. Space Cloud uses its in-built eventing system to guarantee that all changes irrespective of any network failures propagate to the clients over a bi-directional link in an orderly fashion.

Isolating the database querying and the realtime module helps it scale the realtime piece independent of database. However, this poses some limitations which are acceptable for most applications.


  • The table/collection should have a unique identity (primary key or a unique key) in its schema.
  • All mutations (inserts, updates and deletes) have to take place via Space Cloud.
  • All updates and deletes can be made on a single document only using the unique identity (primary/unique fields) in the where clause.
  • Another request should not update the fields used in the where clause of liveQuery.

Note: These limitations are only applicable if you intend to use the realtime functionality.

Have a technical question?

Improve the docs!