Earlier quoted context omitted.
I did not realize MySQL was also named after one of his kids.
Little bobby tables they called him
[deleted]
K1 Buys MariaDB
51–60 of 94 posts
Re: K1 Buys MariaDB
#52Re: K1 Buys MariaDB
#53It 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.
> as more and more web development has fallen in love with PostgreSQL
As in the hype train? They used to love mongodb in its broken state.
If only most of them actually investigate, compare and evaluate to make this choice.
Re: K1 Buys MariaDB
#54What are some reasons to use MariaDB over PostgreSQL?
My reason has been relative simplicity. PostgreSQL comes off as much more complex (though whether that is actually true is probably dependent on what you're doing with it). I'm also not working with super-high-performance production-critical loads, though, so grain of salt and all that.
Mysql is mercurial, Postgres is git. With mysql everything comes somewhat intuitive. Postgres is antiintutive in a lot of places. Probably the people that created it didn't realize that the complexity of Oracle was not needed but was a job program for expensive consultants /s
Re: K1 Buys MariaDB
#55Earlier quoted context omitted.
My reason has been relative simplicity. PostgreSQL comes off as much more complex (though whether that is actually true is probably dependent on what you're doing with it). I'm also not working with super-high-performance production-critical loads, though, so grain of salt and all that.
Mysql is mercurial, Postgres is git. With mysql everything comes somewhat intuitive. Postgres is antiintutive in a lot of places. Probably the people that created it didn't realize that the complexity of Oracle was not needed but was a job program for expensive consultants /s
My own take:
"With MySQL everything seems somewhat more intuitive at first, until it doesn't. Postgres seems antiintutive in some ways at first, until it isn't."
Re: K1 Buys MariaDB
#56What are some reasons to use MariaDB over PostgreSQL?
All of these sibling comments are listing good technical reasons but the most compelling reason by far that I’ve run into for using MariaDB over Postgres is that the underlying software you are trying to deploy only supports MySQL/MariaDB. When my options are “MariaDB” or “Use an entirely different application” I often opt for MariaDB
Re: K1 Buys MariaDB
#57It 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.
> as more and more web development has fallen in love with PostgreSQL As in the hype train? They used to love mongodb in its broken state. If only most of them actually investigate, compare and evaluate to make this choice.
they learned about jsonb support from postgres so they migrated from mongodb to postgres
Re: K1 Buys MariaDB
#58What are some reasons to use MariaDB over PostgreSQL?
They are honestly equally fine for most use cases. I find MariaDB tooling better and have a lower mental overhead dealing with it, but perhaps I'm just more used to it.
We used to hit a wall when reaching 100bn rows on MySQL but that was 15 years ago.
Re: K1 Buys MariaDB
#59Earlier 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…
> Partitioning has been supported for quite a while
My comment (which you're replying to) didn't mention partitioning at all.
> Logical replication...
My comment specifically said that logical replication of DDL statements is not supported out-of-the-box in FOSS Postgres, which is absolutely accurate. See the very first thing mentioned on https://www.postgresql.org/docs/current/logical-replication-...
You can pay EnterpriseDB for a solution, among other vendors. That situation is far from ideal.
> PostgreSQL has gained autovacuum support.
That doesn't even remotely solve the inherent problems of Postgres's MVCC implementation. See https://www.cs.cmu.edu/~pavlo/blog/2023/04/the-part-of-postg...
Re: K1 Buys MariaDB
#60For 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 ho…
For single instances, this seems very true.
For complex multi-member clusters Maria/MySQL are quite far ahead.