PostgreSQL over MariaDB
Replay ingestion is moving to a pool of Go workers, and the jobs will queue in PostgreSQL. A job starts when someone acts on the site, so the API can notify the workers the moment it adds one, using Postgres’s LISTEN/NOTIFY. MariaDB has no equivalent, so its workers would have to keep checking the table. Keeping the queue in the same database also means a job and the data it belongs to will be saved in one transaction. A separate queue like Redis would be a second write that can fail on its own, leaving a job for data that was never saved.
Leaving the database I had run in production for two years, and putting queue traffic on the same database the site uses.
