Attributes table might grow rapidly leading to performance issue

[thomaschiozzi-tndigit]

Currently the attributes table in the DB can hypotetically have one entry per tuple (entity_id, provider, attr_key), with entity_id ∈ E, provider ∈ P and attr_key ∈ K. The hypotetical maximum size of the table is hence |E|×|P|×|K|.
In use cases where |P|×|K| is big (possibly in hundreads) and |E| is non-trivial or growing over time, this table can reach a considerable size. Since this table can be read & updated multiple times by attributes providers per each authentication, this could lead to perfomance issues.

AAC users might be adviced in adding indexes to the attributes an a provisional solution if they are in a setting where |P|×|K| is big.