[Spike] Determine scalability of using schemas to handle tenants

[exalate-issue-sync]

Determine if using separate schemas per committee will scale appropriately. If we make a schema per committee, will the application perform as desired? If scalability is not appropriate, there will be no follow up. If it does scale, determine a design for our api to:

• utilize the schemas to control access
• set up the schemas
• facilitate new committees
• migrate existing data

---

One red flag from https://django-pgschemas.readthedocs.io/en/stable/overview/ is:

• Scalability: for a large number of tenants (thousands) the schema approach might not be feasible, and as of now, there is no clear way for implementing tenant sharding.

Determine if this is by nature of the specific library or the database. If library, we could use an alternative.

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1888