this post was submitted on 16 Jan 2025
62 points (98.4% liked)

Selfhosted

60587 readers
1586 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hey, Threadiverse! I'm looking for informed opinions on database choices.

I can stand up an Internet-facing application and have it use either MySQL or PostgreSQL. Which is the better choice, and why do you think so?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 14 points 2 years ago* (last edited 2 years ago)

Postgres. It's more strict by default, which leads to a lot fewer surprises.

Here's my rule of thumb:

  1. SQLite - if it's enough
  2. Postgres
  3. MariaDB - if you don't care about your data and just want the thing to work
  4. MySQL - if you sold your soul to Oracle, but still can't afford their license fee
  5. Something else - you're a hipster or have very unique requirements