Rule 1: Developing a good DBMS requires 5-7 years and tens of millions of dollars.
That’s if things go extremely well.
Rule 2: You aren’t an exception to Rule 1.
And yes, things like top level transaction databases are like hand maintained clusters of 20 servers for the whole Alibaba with query caching servers in front of them to prevent OOMs
They tried to get rid of it many times as written in their tech blogs, but this probably indicates that they finally gave up on such endeavour, choosing to own Mysql instead
If you time-atomize the transaction, you get increase in minimal latency.
If you simply use a single server with very fast DB, you get reliability concerns.
With token ring locking, you get both.
And so on, so on, and on
EnterpriseDB: $64.92M in 6 Rounds from 7 Investors
Plus it is much more under development than 5-7 years.
20 years * LoadedLaborCost (USD$150k/personyr) * 10 people
I think you could relate that to funding?
RocksDB from Facebook, ColumnStore, MaxScale...really cool stuff.
It's a fork as much as the stable packages that RedHat or Debian ships are "forks" since they have a few patches applied to customize for their environment and fix a few issues that hadn't made it upstream by the time they picked a stable release to base on.
MariaDB is an active, independently developed project. They are probably funding MariaDB because working with upstream developers of an actively developed fork can be more efficient than striking out on their own with another actual fork. I wouldn't be surprised if they eventually start using MariaDB, and either rebase their AliSQL patches on top of it or drop AliSQL altogether (much of it just looks like backports of bugs or features).
> Moreover, it includes patches from Percona, WebScaleSQL, and MariaDB.
(see (google) Bigtable vs (amazon) Postgres)
Dynamo might be a slightly closer comparison
databases people know and use already (eg in fun projects) are easier to sell
A more detailed intro (in Chinese) can be found at http://www.infoq.com/cn/news/2017/08/ali-polardb.
Alibaba has developed another DB called OceanBase (open source).
One can say about Google / Facebook / Amazon investing in startups and non-profits inevitably influence these organizations' directions; that's just the nature of any investments. When you donate money to a cause you support, you indirectly influence how the cause is headed, because you can pull the pledge, and when enough people pull the pledge, then the people running the cause/non-profits will have to do something to the demand of the donators.
China is the biggest creditor of the US national debt, and even before that US was careful with its relationship with China anyway. So we can't say there is a cause and effect, the best is a weak correlation, and even that is a stretch.
China is the biggest creditor to the US national debt
Do you want me to be more precise? Foreign creditor?
"The Treasury Department has ranked China as the biggest foreign creditor to the U.S. for the overwhelming majority of the past nine years. "
That's not being more precise. That's something entirely different.
(Not agreeing or disagreeing with you, just kind of funny/ironic that we're talking about a fork of an open source project that exists because of disagreement with the steward of MySQL... if Alibaba negatively impacts MariaDB, couldn't we just then move on to another fork. MylantaDB anyone?)
Monty is the one who first created MySQL, and later foked MySQL to create MariaDB. There is also MaxDB, but it looks to be a SAP product.
It's open source- when that happens, you can fork it and influence it in the direction that you like. I mean if the GCHQ has an active github account - I think the PRC gets a pass to publish open source, let alone Alibaba.
Yes, but the Western governments are moving in a similar direction. I'd rather Alibaba sponsor MariaDB than not.
I suspect they’ll treat it like a piece of critical infrastructure; their political concerns would be at the gfw level, and I just don’t see the likelihood of weaponized attacks. Databases are usually locked down for egress and any outgoing attempts would be rapidly detected.
Only if the backdoor is obvious. I doubt they would introduce a backdoor that reads
`if ($PWD = "supersecretbackdoorpwd") loginAs("root");`
But a subtle buffer overrun resulting in a 0day that's only obvious to the writers - that's much more likely.
Check out the Underhanded C contest for examples of ways exploits can hide in plain sight.
EDIT: I'm not saying that's what going to happen with Alibaba & MariaDb. I'm just saying that "open source" != "free of exploits and backdoors". One of the biggest untruths about open source is that, with enough eyeballs, all bugs are shallow.
This kind of stories doesn't seems to hurt the US HDD maker 's brand, neither.
Most of the world just don't care or don't have a choice.
- MariaDB MaxScale 2.0 will be under the BSL.
- MariaDB Server will continue to be licensed under GPL in perpetuity, while its connectors will continue to be under the LGPL.
To be honest I cannot blame Monty. Google and Facebook were built on MySQL and probably didn't give back as much as he thought would be a fair shar. I guess he doesn't want to see this happening again.
The problem is all these people going into headless chicken mode about how Oracle could discontinue the open source licence of the “original” MySQL, so they’re embracing MariaDB (the company) because it’s run by Monty so it must be open source friendly.
You can use/support MariaDB all you want but let’s not pretend they’re great bastions of open source compared to Oracle in the MySQL realm.
As I said, I just made a clarification on that “new code” means other products and not MariaDB server.
Just for the record I am not a MySQL-based DB user, so I don’t really care at all about MariaDB or BSL. My license of choice for releasing my code is AGPL.
If the MariaDB MaxScale licensing bullshittery didn’t make you think twice about relying on MariaDB, why do you worry about Oracle?
(If you put some (throwaway?) contact email in your profile I'd be interested to trade stories/old gossip via phone over the weekend; it seems like we worked in similar markets over similar times.)
Meaning, he's probably limited his investments into the new company.
Uber (I know, I know) switched to MySQL, here are some reasons why:
Re: Why Uber Engineering Switched from Postgres to MySQL | https://news.ycombinator.com/item?id=12179222
Why we lost Uber as a user | https://news.ycombinator.com/item?id=12201353
> naming / pronunciation diversion: https://news.ycombinator.com/item?id=12201672
Did they ever clarify what data actually caused the issues?
It's something we should at least consider an issue, even if it doesn't feel like a valid technical issue.
not sure if galera cluster is a good thing.. we've started out with galera and it was a pain. we now run on postgres, but even if we would've stayed with mysql we wouldn't use galera anymore. network split was a pita, even if you had major quorum.
To be fair, uber did get burned by a Postgres replication failure- but they also had a NOC team promote 3 bad replicas to primary before stepping back to reconsider their approach. Carpenters do hate losing their fingers in circular saws.
MySQL/MariaDB is pretty much the "standard" database that most programmer started with. At least in university.
So there is no point on using PosgreSQL if MariaDB fits the bill for them. Less learning curve, easy to hire for etc
* you can configure triggers for a table, but you can't use them in MySQL unless you make sure the table is InnoDB (this was a while ago before defaults changed)
* MySQL doesn't support aborting INSERT/UPDATE/DELETE from trigger, but you can emulate it by throwing an exception
* a table can have a CHECK constraint, but you can't use it because it is not available in MySQL
Makes one wonder MySQL was picked for that class. I get that it was because it was very popular at the time, but it felt like a toy compared to a functionality that any other database had.
I'm interested in what people's experiences here are. I spent the entire of my degree deep in Oracle, persistently being warned a database without object-relational queries were absolutely never used in the real world (how ironic).