The idea of creating pre-populated (and updating) circles is very interesting, but I wonder how it scales. What if I have thousands of employees to sync nightly? Creating and maintaining circles for all of them seems like it could be taxing on the system once the number and size of circles reaches a certain point.
Example: Employee A has a circle with Employees B and C. Employee B has a circle with Employees A and C. Employee C has a circle with Employees A and B.
That's three circles to maintain, each with three members within to also maintain (if Employee A changes teams, I have to update these three employees, plus all of the employees of the new team). That's manageable, but several hundred circles with dozens of members each is going to mean a lot of processing.
Is there a similar API to have employees join a community, or a page? That would be more of a one-to-many relationship rather than many-to-many and could be a lot easier to manage.
Example: Employee A is a member of Community 1. Employee B is a member of Community 1. Employee C is a member of Community 1.
Under this model, if Employee A changes teams, I only need to update one membership.
1 comment :
The idea of creating pre-populated (and updating) circles is very interesting, but I wonder how it scales. What if I have thousands of employees to sync nightly? Creating and maintaining circles for all of them seems like it could be taxing on the system once the number and size of circles reaches a certain point.
Example:
Employee A has a circle with Employees B and C.
Employee B has a circle with Employees A and C.
Employee C has a circle with Employees A and B.
That's three circles to maintain, each with three members within to also maintain (if Employee A changes teams, I have to update these three employees, plus all of the employees of the new team). That's manageable, but several hundred circles with dozens of members each is going to mean a lot of processing.
Is there a similar API to have employees join a community, or a page? That would be more of a one-to-many relationship rather than many-to-many and could be a lot easier to manage.
Example:
Employee A is a member of Community 1.
Employee B is a member of Community 1.
Employee C is a member of Community 1.
Under this model, if Employee A changes teams, I only need to update one membership.
Post a Comment