|
|
|
|
|
|
by nivla
4612 days ago
|
|
|
The main stronghold of MariaDB is the drop in replacement for MySQL. If you already have a well established web app and you are planning on get off the clutches of Oracle, MariaDB is your easy choice. You don't have to make substantial changes or worry about breaking any existing functionality. As for performance, can someone who have used both comment on it? Also anyone knows if any exciting changes coming to MYSQL? Can't believe MySQL still doesn't have support for Json. |
|
|
I have to agree that MariaDB's main stronghold being MySQL drop in. The other MySQL drop in out there is MemSQL, which is closed and they really keep pricing under wraps.
TokuDB is a great engine. I don't think Postgres has a storage engine that matches the benefits TokuDB brings, but other than that I don't see many benefits over Postgres for a new project, but haven't compared the replication features closely.
Migrating a big codebase to Postgres from MySQL can be kind of a pain unless everything wrapped everything in an ORM like sqlalchemy. The main pain point for me in a recent migration was how postgres handles mixed case in table/column names. Most of the function differences between the two are fairly easy to resolve.
Can anyone with experience with JSON in both Postgres and MariaDB make a comparison?