MySQL or SQL Server?

PostgreSQL

No sql. No nosql either.

For what? It's usually decided for you by the existing infrastructure, and I can't imagine whatever dba has to maintain it will be delighted with one in a different setup

For relational. Mariadb

Depends on compatibility requirements.

Is the DB primarily serving a backend web/API framework? Will you use an ORM?

Will there be any secondary consumers, ETL, business intelligence, SaaS visualization dashboards, etc?

Many frameworks & ORMs claim to support a wide range of databases — but some popular community plugin might only work with MySQL in practice.

All else being equal, I prefer Postgres over MariaDB & MySQL for relational databases.

MySQL8 has redeemed MySQL a bit for me, it's not as garbage as it used to be.

I'm a bit of a Redis addict as well.
Different purpose, but use cases go well beyond "in-memory key value cache".

It's indeed a question of the ecosystem, the target and your budget situation.

SQL server has many strengths, as MS left the Win only platform and supported it on linux, it became easier to integrate.

Price aside, the question is: are you able to utilize SQL server?

It's feature set is dependent on a license... But still a large part of it's features are highly specific for "data processing", e.g. R support / reporting / analysis / ....

MySQL is still free, but has - compared to SQL server - far less features. It has a sufficient feature set, as you get the full SQL standard.

Bothersome in my opinion is Oracles shitty QA and intransparency. Expect things to break. GA means for Oracle: It ran through our test suite, if it breaks, it's okay. GA can have new features and be incompatible.

MariaDB and MySQL are seperate products. MariaDB is free.

MariaDb is focused more on robustness and simplification compared to Oracle. Last releases, e.g. 10.5 / 10.6, were largely cleaning up and trying to slim down the codebase. MariaDB has, like MySQL, a sufficient featureset. Additionally it's rather transparent and tries to go back to the root of being simple and powerful, plus it has a nice community around it.

https://mariadb.com/kb/en/...

Postgres is unique. It has a lot of features and has, especially in the last versions, put an extreme focus on performance.

I dislike Postgres a bit because it is ... A bit much academic. It doesn't pamper you. Do your homework and it will be a good database, with a large featureset, good SQL standard implementation and a heavy focus on threaded performance. But you have to be diligent. If you expect it to be simple and ease to use, I've got bad news for you.

Your mom

SQLite

What

CSV formatted txt files. In an external SD card. Formatted in FAT16. On a remote location. With 2Mb/s of upstream limit.

@c3r38r170

Build a wheeled robot which can arrange colored m&ms on the floor of a warehouse.

It has a set of internal tubes with m&ms sorted by color, it can suck up m&ms into the correct tube, deposit them in a precise spot, and observe which color is straight under it.

A spot can be empty, brown, red, orange, yellow, green or blue, so that's a septenary digit system.

So at 0.85g/m&m that's about 96.3 megabyte per semitruck with 30 metric tons of candy.

Of course, you should add a lot of parity bits in case of mice.

After that, I think you should run Redis on your m&m storage, because Redis performs very well.