[Enhancement]: Switch to Postgres

[mrjvs]

Checked Existing

• I have checked the repository for duplicate issues.

What enhancement would you like to see?

Mongodb has it's issues and it's starting to show on Juxt.

We will be using the Prisma ORM, used only on the new Juxt-API project.

This is going to be an incremental change, slowly collections will be moved. Not all in one release.

Any other details to share? (OPTIONAL)

The main problems that we have encountered:

• You can't relate data properly in mongodb and juxt needs to maintain a lot of relationships, a few examples:
  • A post has likes, which has a user.
  • A post has a reply, which has a user
  • a community has posts, which has replies, which has users
  • All of these relationships are very hard to join together efficiently - the solution to this has been to just copy paste the data you need joined also in the other datatype (copy paste user data into a reply). But this gets out of sync, you can no longer update a mii image by changing one field.
• Schema-less data easily gets out of sync, especially when running it in two separate services (miiverse-api, juxtaposition-ui)

Mongodb performs well in terms of speed, but it comes at the cost of development speed and data consistency. It's not a good fit for juxt.

[jonbarrow]

Mongodb has it's issues and it's starting to show on Juxt.

Can you provide any examples of this which aren't user error? Mongo has been working just fine in arguably higher traffic servers like the account server, and nearly every issue we've had with Mongo has been user error or some other issue unrelated to the database itself