Multi-tenancy
With more clubs using the project and the server processes getting fatter we should really take a look at multi-tenancy.
- Isolated Approach: Separate Databases. Each tenant has it's own database.
- Semi Isolated Approach: Shared Database, Separate Schemas. One database for all tenants, but one schema per tenant.
- Shared Approach: Shared Database, Shared Schema. All tenants share the same database and schema. There is a main tenant-table, where all other tables have a foreign key pointing to.
This package does number 2. which seems the best approach for this project.