What are some reasons to use MariaDB over PostgreSQL?
For a legacy system originally built on MySQL back before Postgres was so strong.
K1 Buys MariaDB
11–20 of 94 posts
Re: K1 Buys MariaDB
#12It must be tough for the business, as more and more web development has fallen in love with PostgreSQL. While the support business for PostgreSQL exists, I am not sure if they can get similar profit margins / earning multipliers as early 2000 software businesses, even open source ones.
[flagged]
Re: K1 Buys MariaDB
#13What are some reasons to use MariaDB over PostgreSQL?
They’re both great systems but there are a few differences primarily in small ways for most applications:
Maria supports partitioning, Postgres (as of my last knowledge) does not.
Unstructured data is more flexible in Maria natively, but Postgres can support it in a variety of ways.
You can find lists and lists of head to head comparisons out there which will highlight all of the niche differences that each brings over the other.
Ultimately either will work just fine for 99% of use cases.
Re: K1 Buys MariaDB
#14Re: K1 Buys MariaDB
#15It must be tough for the business, as more and more web development has fallen in love with PostgreSQL. While the support business for PostgreSQL exists, I am not sure if they can get similar profit margins / earning multipliers as early 2000 software businesses, even open source ones.
[flagged]
Maybe you have misconception about the scalability of PostgreSQL.
> According to Instagram representatives, the number of platform users exceeded 2 billion last year. This is quarter of all humanity. This mass of people publishes nearly 50 million photos a day. Football star Cristiano Ronaldo has over 600 million followers; singer Ariana Grande has over 380 million. Talk about huge databases!
> Instagram uses many RDBMSs, but PostgreSQL and Cassandra were chosen for the main tasks. The goal was to reduce delay and ensure users can easily and comfortably use the application.
PostgreSQL is also the most popular database in StackOverflow surveys.
Re: K1 Buys MariaDB
#16For those who are using MariaDB in a business context: does this make you more or less likely to choose it for your next project? I don't know anything about K1, so all I have is confusion (and a sudden urge to switch entirely to postgres).
From my POV, it's a supplier that is no longer beholden to shareholders demands for profit. A platform and service that can operate using customer sourced revenue and respond to market demand without a profit driven board is a big win for everyone while funding development and maintenance of a great open source project.
Re: K1 Buys MariaDB
#17What are some reasons to use MariaDB over PostgreSQL?
At scale, there are some workloads where it can be a great choice:
* InnoDB (default storage engine in MySQL and MariaDB) uses a clustered index, which can handle an extremely high volume of primary key range scan queries
* Ability to handle several thousand connections per second without needing a proxy or pool (the connection model in MySQL and MariaDB is multi-threaded instead of multi-process)
* Workloads that lean heavily on UPDATE or DELETE have terrible MVCC pain (vacuum) in Postgres, rarely a problem in MySQL or MariaDB due to using an undo log design
* Support for index hints and forced indexes, preventing huge outages when the query planner makes a random mistake at an off hour
* Built-in support for direct I/O is important for very high-volume OLTP workloads -- InnoDB's buffer pool design is completely independent of filesystem/OS caching
* If you need best-in-industry compression, the MyRocks storage engine is easy to use in MariaDB
* Logical replication can handle DDL out-of-the-box in FOSS MariaDB or MySQL, whereas in Postgres you must pay for an enterprise solution
* Much better collation support out-of-the-box
* Tooling ecosystem which includes multiple battle-tested external online schema change tools, for safely making alterations of any type to tables with billions of rows
* MariaDB has built-in support for using system-versioned tables, application-time periods, or both (bitemporal tables)
That all said -- Postgres is an amazing database with many awesome features which MariaDB lacks. Overall unless your situation is very high scale or an unusual edge-case, it's usually best to just go with what you know / what your team knows / what you can hire for, etc.
Re: K1 Buys MariaDB
#18Only question is will it remain open source and free.
Re: K1 Buys MariaDB
#19Earlier quoted context omitted.
I did not realize MySQL was also named after one of his kids.
Yeah, "My" is actually pronounced wrong by 99% of all MySQL users.
Sure, but
> The official way to pronounce “MySQL” is “My Ess Que Ell” (not “my sequel”), but we do not mind if you pronounce it as “my sequel” or in some other localized way.
Re: K1 Buys MariaDB
#20Earlier quoted context omitted.
[flagged]
Maybe you have misconception about the scalability of PostgreSQL. > According to Instagram representatives, the number of platform users exceeded 2 billion last year. This is quarter of all humanity. This mass of people publishes nearly 50 million photos a day. Football star Cristiano Ronaldo has over 600 million followers; singer Ariana Grande has over 380 million. Talk about huge databases! > Instagram uses many RD…
"popular with developers" is not the same as actually used in real world scenarios. Show me a real world example of pgsql failover and re-mastering that does not involve a restore and not editing configs. How basic? Not even sybase ASE server needs that. Ingres made change in the 80's, everyone else copied it and built on it. Except postgres. It's the Minix of databases.
Show me any proof, that anything of scale is happening in postgresql. All that big facebook and apple data is happening in cassandra (and foundationdb for apple). Netflix has the same pattern, MySQL and Cassandra. Like the days of yore of keeping big data in file systems or tapes and blob indexes in a RDBMS.