Migrate database from MSSQL to Postgres #529
Description
While MSSQL is preferred due to the usage of Azure and the heavy Microsoft environments, Postgres has some advantage both from a cost perspective, and functionality. The GraphQL engine (Hasura) was built with Postgres in mind, and while their MSSQL support has come a long way, Postgres still offers lots of additional and better supported features.
From a cost perspective, while Postgres databases are more expensive on a per-database basis, the power that each instance offers is multiples more powerful than the equivalent MSSQL tier. Ultimately a multi-region deployment arrangement will be more expensive with Postgres, but the power each region will have is substantially better than that of MSSQL. The cost for performance ratio is much more favorable to Postgres, assuming the site maintains levels of traffic that properly utilize each database.
From this perspective, some research will need to be done on amount of athletes in each region to determine where to place database instances. We can use existing PowerBI reports on USA Fencing membership to inform on where to place database instances to make most of the increased performance, without over investing in regions which might otherwise be underutilized.