Figure out Backend Data Models

[jaohara]

We're going to need to figure out how we want to store our data.

I'm thinking that we'll need both a database and filesystem/blob storage for this application:

• Uploaded files are stored in whatever blob storage system is used
• DB table for File metadata (name/type/timestamp/contest reference/user reference/
• DB table for User data (name/bio/location/profile picture/social links)
• DB table for Votes (reference to User and reference to File)
• DB table for Contest data (timeframe/theme/etc.)

Questions

• Do we need to store the results of each completed contest, or could we just sum up all votes that reference a given contest?
  • Caching the results would be more efficient as they won't change outside of the contest window
• Do we have a ORM (Drizzle?) that we could use to make accessing our models easier?

Any other thoughts? We could probably normalize some of those tables if we want to be more efficient/lose our minds

[jlsnow301]

Drizzle does make this a bit easier. We write the schemas in TS and it will infer types for us. As for database host - I'm familiar with supabase, and it'd be quick to get going. They also offer file storage options, but perhaps @Exochos would have a more barebones solution than the managed option

[Exochos]

Docker + Postgres free open source and well supported. Pgadmin if we want a dashboard for it