watch() function for tigris objects

in FoundationDB, there is the option to watch a key. I would like to express strong interest in having access to this for any given Tigris object.

This would be different to the object notifications that are already provided because this would allow a specific process to watch for and be triggered by changes. In contrast, object notifications come into the application from the outside, making it difficult to link up individual processes to the external activity.

Tigris gives us conditional operations which alleviates much of the database work previously required to maintain strong consistency. Watch() feels like the complement to this. A strongly consistent watch on a per-process basis. This would allow us to remove all of our reliance on a traditional database and use only Tigris object store as a performant, efficient, cost-effective, bottomless object store. The ideal object store.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.