MariaDB vs PostgreSQL: What are the differences?
MariaDB: An enhanced, drop-in replacement for MySQL. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance; PostgreSQL: A powerful, open source object-relational database system. PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
MariaDB and PostgreSQL belong to "Databases" category of the tech stack.
"Drop-in mysql replacement", "Great performance" and "Open source" are the key factors why developers consider MariaDB; whereas "Relational database", "High availability " and "Enterprise class database" are the primary reasons why PostgreSQL is favored.
MariaDB and PostgreSQL are both open source tools. It seems that PostgreSQL with 5.38K GitHub stars and 1.79K forks on GitHub has more adoption than MariaDB with 2.79K GitHub stars and 856 GitHub forks.
According to the StackShare community, PostgreSQL has a broader approval, being mentioned in 2701 company stacks & 2098 developers stacks; compared to MariaDB, which is listed in 496 company stacks and 453 developer stacks.
What is MariaDB?
What is PostgreSQL?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using MariaDB?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
In my opinion PostgreSQL is totally over MongoDB - not only works with structured data & SQL & strict types, but also has excellent support for unstructured data as separate data type (you can store arbitrary JSONs - and they may be also queryable, depending on one of format's you may choose). Both writes & reads are much faster, then in Mongo. So you can get best on Document NoSQL & SQL in single database..
Formal downside of PostgreSQL is clustering scalability. There's not simple way to build distributed a cluster. However, two points:
1) You will need much more time before you need to actually scale due to PG's efficiency. And if you follow database-per-service pattern, maybe you won't need ever, cause dealing few billion records on single machine is an option for PG.
2) When you need to - you do it in a way you need, including as a part of app's logic (e.g. sharding by key, or PG-based clustering solution with strict model), scalability will be very transparent, much more obvious than Mongo's "cluster just works (but then fails)" replication.