Skip to content

Mapping Organization User

Masterxilo edited this page Oct 12, 2012 · 4 revisions

How about, instead of

  • having the user and the organization store their members/memberships (for performance)
  • or having only one of them store the list and require looping for the other

having a list of links between organizations and users?

Advantages

  • There's no need to argue about whether it makes more sense to put the list to both or which one of them.

Disdvantages

  • Slower than having lists on both the user and org side.
  • Compared to having a list in either agent-type: Slower for the side that would have the list (e.g. listing all members of an organization would be faster if the org stored it's members list), as fast for the other side (user would still have to loop through all orgs and their lists to find the orgs he belongs to).

So overall slower.