MariaDB to go public at $672M valuation
mariadb.com
mariadb.com
No matter how I turn and adjust the parameters, MariaDB seems to be the least popular of the big databases on the market today (https://trends.google.com/trends/explore?date=today%205-y&q=...) and looking long-term (2004-preset), it seems like it's popularity is going down, not up (https://trends.google.com/trends/explore?date=all&q=MariaDB).
I wonder what metrics they are looking at to figure out that it's "Fast Growing", under "Viral adoption" and "A leading relational database brand"? Probably they have some insight that I don't, or this is just a press release filled with the usual marketing lies.
I'm not necessarily saying your opinion at this moment in time will change, only that you should re-evaluate it occasionally.
Word Perfect works with Word, but Word doesn't work with Word Perfect.
Definitely typical marketing lies. They're IPO'ing precisely because it's a very good time to get out. There's no more upside left in MariaDB as a database/brand/business and the stock market is still high.
Edit: in fact I think that if you search "default" on this page these are all the distros that do this. https://mariadb.com/kb/en/distributions-which-include-mariad...
https://mariadb.com/kb/en/incompatibilities-and-feature-diff...
While they're still quite similar and many of the differences might not be something that you hit, there are enough differences that it should be explicit.
Regardless, where possible, I use non-relational. When relational is required, I use Postgres.
This article put it really well in my opionion: There are no schemaless databases, just the ones with an explicit schema and the ones with their schema defined in a couple hundred places in code.
One of them is slightly easier to start out with, the other to evolve, maintain and communicate (double serving as self-documentation) across multiple engineers.
https://orangematter.solarwinds.com/2015/02/24/schemaless-da...
A lot depends on the data you have, and the data you anticipate. If you have well-controlled data sources, sure, 3rd normalized form and tables with JOINs.
But sometimes you have to deal with the data you're handed. Denormalized and only, at best, semi-structured. Then it's time for NoSQL.
i.e., choose the right tool for the data you have and the queries you need. Don't try to force-fit the data to a tool just because you're used to it.
Analogy: use a hammer for a nail, and a screwdriver for screws.
Other structured data could be simple key-value stores, tabular row-and-column stores (single table, no joins), and even graph data models. Like, an Excel spreadsheet is "structured." But it's not a SQL RDBMS.
All of which are basically "NoSQL" though you can shove it in an RDBMS if you want. Just as you can slurp an Excel spreadsheet into a RDBMS. Still doesn't make Excel "relational" per se.
Can you cite a source that shows the opposite to be true?
Source: 80% of global data will be unstructured by 2025 [citing IDC] https://www.analyticsinsight.net/the-future-of-data-revoluti...
I don't have $4,500 to throw at IDC right now, but their latest in 2021 shows that "structured" data, while still smaller than unstructured data in absolute volumes, is now growing faster than the unstructured data. Basically by tagging it with metadata. (I guess that gives a video "structure?") But this metadata management can be done by use of NoSQL, as is popular within IIoT spaces, or by streaming OOT video providers, not just by throwing all data into an ACID-compliant, locking and blocking transactional RDBMS.
Blame the developer who spread data specs in many places, not the database.
The application should have a single interface to interact with the database, hiding the implementation. All data specs should do in a single place, inside this interface.
This is a false dichotomy - there are better ways of self-managing the schema than "couple hundred places in code." There are valid usecases where a schemaless db is the better option (e.g. when you're recording self-describing data. Or when there is an implicit, consistent structure to the data - but the engineers won't know it at development time. Or when you want to do a full-take of structured data including unknown fields without losing data that's not in your DDL without resorting to file blobs, requiring additional data management)
It let lazy "coders" churn out simple brochure sites without having to think.
(The package name is moderated by the FreeBSD ports team, but the port (MariaDB) installs its service and gives itself whatever service name it desires.)
I build schema management software for MySQL and MariaDB, https://www.skeema.io, used by several hundred companies. Among my userbase, MariaDB is a tiny minority, to such an extent that I wonder if it's worthwhile to continue keeping up with their new quarterly release schedule.
The Skeema CLI is able to accurately identify your database version and flavor (which is necessary for its functionality), there is no notion of MariaDB registering itself as MySQL. But the CLI does not contain telemetry, so I don't have hard stats on MySQL vs MariaDB usage.
Wow, this sounds extremely useful, great job! Does anyone know anything like this for Postgres?
Migra is Postgres-specific. Its model is similar to Skeema's, in that the desired-state CREATEs are run in a temporary location and then introspected, to build an in-memory understanding of the desired state which can be diff'ed against the current actual state. (This approach has also been borrowed by other recent tools, including Prisma Migrate [3]). In this manner, the tool doesn't need a SQL parser, instead relying on the real DBMS to guarantee the CREATE is interpreted correctly with your exact DBMS version/flavor/settings.
In contrast, sqldef supports multiple databases, including Postgres and MySQL (among others). Unlike other tools, it uses a SQL parser-based approach to build its in-memory understanding of the desired state. As a DB professional, personally this approach scares me a bit, given the amount of nonstandard stuff in each DBMS's SQL dialect. But I'm inherently biased on this topic. And I will note sqldef's author is a core Ruby committer and JIT author, and is extremely skilled at parsers.
[1] https://databaseci.com/docs/migra
[2] https://github.com/k0kubun/sqldef
[3] https://github.com/prisma/prisma-engines/blob/main/migration...
> These days, most smaller users go with a managed DBaaS such as AWS RDS
I think there's likely a long tail of small (non-tech) businesses that run WordPress (or Drupal/Joomla) on a traditional shared web host (the kind that only offers PHP and MySQL/MariaDB).
Do they, do? I expect all small stuff to be on old school VPSes with included managed DBs.
Has the world of cheap PHP hosting finally moved on? I'd be super surprised.
No 90% of wordpress which is 60% of the internet use small local hosted mysql instances. No they don't setup a vm on aws.
Anyway, among WP usage, I would confidently wager that the percentage running in "cheap VPS" setups is declining fast each year. Many different reasons for this. The heyday of smalltime independent bloggers (on WP or otherwise) was a decade ago. Large SaaS hosts (including the official wordpress.com) make up a big chunk of WP hosting. Security is a huge issue with self-hosted WP. Companies using WP as a CMS aren't going to use a tiny VPS.
There are still a lot of WordPress instances on cheap VPS setups, don't get me wrong. I just don't believe it's still such a major force where it would make up a majority of new mysql/mariadb installations anymore.
> WordPress is used by 65.3% of all the websites whose content management system we know. This is 43.3% of all websites.
Other kinds of DBs it's all over the shop, but yeah, PG seems very dominant here...
Facebook: https://engineering.fb.com/2021/07/22/data-infrastructure/my...
It depends pretty much where one bounces around.
I think you were thinking about YugabyteDB which is a wrapper/fork around Postgres.
MySQL, for example, isn't in debian any more. And hasn't been for years.
All thanks to oracle, of course.
As well, most people search for mysql, when looking for mariadb issues.
Mariadb is far, far more popular than mysql these days.
It depends greatly on what metric you're using. If you look at the huge list of large, well-known tech companies using MySQL, nearly all of them are literally using MySQL (or a derivative like Percona Server), not MariaDB.
In combination these companies employ several hundred thousand engineers, building products on top of MySQL, not MariaDB.
Had Oracle completely abandoned MySQL like they did with Solaris it would have been an easier choice to move to Maria. Instead they nurture it like they did with Java.
Although I am wondering if they will ever release 9.0.
Most mainstream OSes are yet to catch up to Solaris SPARC on this regard.
But I echo the other comments in that I search for MySQL even if I’m using MariaDB.
I think SQLite came close to challenging it in the early 2010s with it's mobile app adoption.
Btw Shodan Trends (https://trends.shodan.io) is available to members as well. Membership costs a one-time payment of $49 for a lifetime account upgrade (https://account.shodan.io/billing/member). You can only do 100 Trend queries per month (if it's not yet cached) but it doesn't require a subscription.
https://jacksonkearl.github.io/HackerTrends/?query=%22mariad...
https://db-engines.com/en/ranking_trend/relational+dbms
MariaDB is the 8th most popular SQL RDBMS.
MySQL is definitely far more popular, as is PostgreSQL, but MariaDB still continues to rise in popularity (107.11 now, up +13.22 in the past year), though its relative ranking remains at #12 on the overall list:
https://db-engines.com/en/ranking
[EDIT: MySQL fell -28.69 to 1214.68 in the past year. PostgreSQL rose +58.42 to 609.38 in the past year.]
• MySQL's drop in the index was only 4.5%
• PostgreSQL's rise was 9.5%
• MariaDB's rise was 12.3%
You linked to a page that charts the relative prevalence of product-names in Google searches.
That's not popularity; that's just googlers choosing the search term they think is most likely to find them the result they want.
Respect.
I was the interface between Oracle Sales and management at a start up a long time ago. It was weird. They offer technical help to use their API, (so its harder to switch away, I was told by my boss). We were on using on a trial basis. They seemed to want to charge based on CPU speed of the computer installed on. The startup ran out of money...
https://www.e-channelnews.com/sun-microsystems-to-acquire-my...
https://www.oracle.com/corporate/pressrelease/oracle-buys-su...
But it was close 2008 and 2009 I believe.
He has three children, so we've got one more go at this with a MaxDB if needed.
edit: I was wrong -- He already used MaxDB previously. We're out of names.
I'm going to be spending a long while contemplating this. My. That's so sweet.
Here, the word yxa (axe) comes close. https://translate.google.com/?sl=sv&tl=en&text=yxa&op=transl...
Edit: Found someone saying the name My, as in Lilla My from the moomins https://forvo.com/word/lilla_my/
[1] https://en.wikipedia.org/wiki/Michael_Widenius#Personal_life
I'm having trouble with YourSQL, but its now MySQL problem :(
https://www.confluent.io/blog/license-changes-confluent-plat... https://blog.timescale.com/blog/building-open-source-busines...
I don't think there is any place for GPL in databases and similar software, specially if it is to be built and run by for-profit companies.
... then, most likely, Linux would never have taken off as contributors would have balked at the copyright assignment bureocracy, as well as not wanting to contribute to Linus's get-rich-quick scheme (why should Linus get special rights to profit of the work of the community?).
Do I misunderstand the copyright status of MySQL/MariaDB, or has MariaDB been clever about how it adds features to the GPL core, such that they're not legally derivative works?
``` $ yum install mariadb-server
Loaded plugins: langpacks, ulninfo
Package mariadb-server is obsoleted by mysql-community-server, trying to install mysql-community-server-8.0.26-1.el7.x86_64 instead
Resolving Dependencies ```
There is a work-around but the way they picked up the word is kinda shocking...
Case in point: most SPACs have fallen anywhere from 50-70% (evtol/lidar/battery companies) over the past year due to the fact that most don't have either a working product or poor numbers
Much better than gargantuan privately held companies where all the gains are going to a small group of capital holders.
source: I've been working in this space for 19 years, at scales ranging from tiny startups, to largest known mysql installation in the world.
Separately you can search for "What's new in MySQL 8" type posts, nearly everything there is unique to MySQL. Some of the 5.7 stuff too, like native json column type.
Ditto for recent MariaDB releases, btw! To be fair they have some cool stuff that MySQL lacks, such as system versioned tables, Oracle DB compatibility layer, native column types for uuid and inet6 (IPv6 addresses), etc.
At least a significant difference is MariadDB's addition of several specialized engines - see https://mariadb.com/kb/en/storage-engines:
- MariaDB ColumnStore: Column-based
- Mroonga: Full text search
- OQGRAPH: Graph storage
- SphinxSE: Full text search
Where the above use cases are required, it's actually a big deal. A common use case may be FT searches - MySQL's support is a trainwreck, and I have the suspicion that Oracle has little to no interest in it.
One thing I wish were available was a hybrid btree and inverted index. If you are multi tenant then you want your search to only happen within the one user’s data — not across all accounts and then filter for the one user.
- MongoDB
- Snowflake
- Databricks
These 3 are probably the biggest, but there are few others which are promising: Cockroach Labs, Materialize, PlanetScale, Yugabyte.
If you invested you would have made a nice chunk of change. MongoDB does have a hosting service though which could be driving a decent chunk of revenue.
Edit: let me explain. Larry bought mysql to save oracle from being outcompeted by a young entrepreneur. Who left after 2 years to create an even more competent DB. To add insult to the injury, this market value is below what they paid for mysql 15 years ago, which makes Larry look incompetent.
(I don't think any of the characters were particularly ethical, smart or otherwise commendable... they just did what people do)
MySQL was originally purchased by Sun, not Oracle. Although Oracle did acquire Innobase Oy (makers of InnoDB, the most popular storage engine in both MySQL and MariaDB) prior to this.
Oracle later purchased Sun, which included other valuable properties (e.g. Java) in addition to MySQL. Naturally this would be a more expensive acquisition than just MySQL itself.
Regardless, the current enterprise value of MySQL (meaning, the MySQL business unit under Oracle) would depend primarily on Oracle's MySQL revenue. This really has no relation whatsoever, in any conceivable way, to the initial listing price of MariaDB's SPAC. These are separate databases with separate userbases, separate cloud DBaaS offerings, separate support contract businesses, etc.
Good luck to MariaDB.
> The Angel Pond SPAC vehicle was founded by CEO and Chairman Theodore Wang, the founder of Puissance Capital Management and Angel Pond Capital and a former Partner at Goldman Sachs, and Simon Xie, the founder and Executive Director of Hangzhou Hupan Shannan Capital Management and a co-founder of Alibaba Group.
If you want public money (via SPAC or IPO), you're paying money to "Wall Street" in one form or another.
Other news:
Adoptium/Temurin is doing FLOSS Java distro under the Eclipse Foundation
Not saying I love Goolge, Facebook or even MS these days, but they seem to play it A LOT nicer that Oracle in that regard.
https://www.theregister.com/2021/09/16/oracle_jdk_free_licen...
It's messy.
OpenJDK of which OracleJDK is just a fork is absolutely free and libre.