RethinkDB changefeeds are great for dealing with data streams which are common to all users, but changefeeds can get tricky when you need to deal with hundreds of thousands of data streams which are more or less unique to each user (or unique to many small groups of users) - This is particularly true when you need to scale your app beyond a single process/instance/machine.
The approach described in this article may not be suitable for a lot of use cases. It's fine if all users shared the same central collection of Fruits (E.g. a giant Fruit basket)... But what if users were divided into many small groups and each group had its own independent Fruit basket? It becomes extremely difficult to manage all these unique changefeeds on the backend (especially if you have to scale beyond a single machine).
The team behind RethinkDB is currently working on a project called Horizon (previously called Fusion) which should solve this problem.
The approach described in this article may not be suitable for a lot of use cases. It's fine if all users shared the same central collection of Fruits (E.g. a giant Fruit basket)... But what if users were divided into many small groups and each group had its own independent Fruit basket? It becomes extremely difficult to manage all these unique changefeeds on the backend (especially if you have to scale beyond a single machine).
The team behind RethinkDB is currently working on a project called Horizon (previously called Fusion) which should solve this problem.