Scaling User Restricted Data

User-restricted access to data is discussed in the docs. In the example each movie record is given an array of users that have the movie on their watch list.

This presents obvious scaling challenges especially with the objective of keeping records small. What if 10,000 users add the same movie to their list?

Can you provide any guidance or best-practices for how to scale this kind of user data?


Hi @Chris_H, If your records became too large you could split them into multiple records and then group them with the ‘distinct’ parameter. In this case, you could use a copy of the record and add half the users to one record and the other half to the second record, then group the records with the distinct parameter on a common attribute.