One post tagged with "reactivity"

Meteor.js has two ways to detect database changes and push them to connected clients: polling and oplog tailing. Polling works out of the box. Oplog tailing performs better but requires a MongoDB replica set. Both have tradeoffs that get worse as your data grows.

Thermocline solves this differently. Its WAL-based change stream architecture gives Meteor applications oplog-compatible reactivity with none of the operational overhead, and adds automatic hot/cold tiering that lets large collections move to object storage without breaking live queries.