Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

K1 Buys MariaDB

prnewswire.com

Post reply on HN
Print view View original

41–50 of 94 posts

Re: K1 Buys MariaDB

#41

Post by mjevans »

evanelias wrote: post #17
lfmunoz4 wrote: post #7

What 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 le…

Partitioning has been supported for quite a while

https://www.postgresql.org/docs/current/ddl-partitioning.htm...

Logical replication...

https://www.postgresql.org/docs/current/logical-replication....

https://github.com/2ndQuadrant/pglogical?tab=readme-ov-file#...

https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatab...

In 'recent years' (in database support terms), PostgreSQL has gained autovacuum support.

https://www.enterprisedb.com/blog/postgresql-vacuum-and-anal...

This stack overflow question was insightful, in that most of the slowness many experience may be related to foreign key check lookups on unindexed columns that point to external keys. https://dba.stackexchange.com/questions/328884/why-is-the-de... Partitioned data and batches to spread out updates also appear to be current best practices https://www.dragonflydb.io/faq/postgres-delete-performance

Re: K1 Buys MariaDB

#43

Post by mathnode »

garciasn wrote: post #13
lfmunoz4 wrote: post #7

What 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 ov…

postgres have table partitions now, mariadb can however partition a table over multiple servers or shards using the engines like spider and connect, or proxies like maxscale and proxsql. Local or remote, read your database manual about the fun and caveats that come from partitions.

Re: K1 Buys MariaDB

#44

Post by AlisdairO »

maxk42 wrote: post #24
lfmunoz4 wrote: post #7

What are some reasons to use MariaDB over PostgreSQL?

MariaDB scales much better, with native clustering support, native partitioning support, as well as better single-node performance: https://www.databasebenchmarks.net/benchmark-charts.html

That link isn't particularly convincing. As far as I can see, the only Postgres test performed on the hardware that the top MariaDB entries had was on a positively ancient Postgres version (9.2.1).

Re: K1 Buys MariaDB

#45

Post by kijin »

steve918 wrote: post #38
evanelias wrote: post #26

Earlier quoted context omitted.

MariaDB Server is GPL and must always remain GPL, as it's a fork of MySQL which was also GPL. Also the MariaDB Foundation is separate from the commercial/enterprise entity MariaDB plc. This article is about the latter being taken private.

This code base has been sold like 3x now and is still around.

If anything, that looks like solid evidence of the resiliency of GPL.

Re: K1 Buys MariaDB

#47

Post by mathnode »

mjevans wrote: post #41
evanelias wrote: post #17

Earlier quoted context omitted.

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 le…

Partitioning has been supported for quite a while https://www.postgresql.org/docs/current/ddl-partitioning.htm... Logical replication... https://www.postgresql.org/docs/current/logical-replication.... https://github.com/2ndQuadrant/pglogical?tab=readme-ov-file#... https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatab... In 'recent years' (in database support terms), PostgreSQL has gained autovacuum support. ht…

Logical replication does exist in pgsql, which is great. What it still lacks however (and I am sure they will very quickly catch up on) is the user facing process of being able to fix or sync a broken node without a rebuild. I'm also pretty sure pgsql logical replication is single threaded? Things like pg_rewind are layered on fixes that other database users don't have to depend on or learn. Except Oracle (because it's a mess).

Re: K1 Buys MariaDB

#48

Post by kev009 »

herbstein wrote: post #42
philipwhiuk wrote: post #39

Earlier quoted context omitted.

He already has Max. MaxDB sounds like good name tbh.

MaxDB is already developed by SAP, weirdly enough, No relation tho https://en.m.wikipedia.org/wiki/MaxDB

There is actually a relation, it used to be called SAP DB and MySQL AB renamed it to MaxDB.

Re: K1 Buys MariaDB

#49

Post by g8oz »

maxk42 wrote: post #24
lfmunoz4 wrote: post #7

What are some reasons to use MariaDB over PostgreSQL?

MariaDB scales much better, with native clustering support, native partitioning support, as well as better single-node performance: https://www.databasebenchmarks.net/benchmark-charts.html

Interesting, I found the page comparing performance on AWS useful.

https://www.databasebenchmarks.net/benchmark-charts.html/?aw...

Re: K1 Buys MariaDB

#50

Post by kev009 »

floating-io wrote: post #8

For 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).

I moved to postgres over a decade ago but have occasionally had to interlope into MySQL/MariaDB infrastructure. IMHO it has been a lesser choice for a long time, typically just clinging onto it because of legacy reasons or an over-involved executive but these people are also typically very proud and protective over the thing they know.

Realistically if you need the MySQL semantics (eww) and wire protocol TiDB or a hosted offering like Aurora DB have been better choices for a long time now.

Post reply on HN