Slashdot Mirror


MariaDB CEO Accuses Large Cloud Vendors of Strip-Mining Open Source (zdnet.com)

Big cloud companies are "strip-mining open-source technologies and companies," complains Michael Howard, CEO of MariaDB. At their developer conference, Howard accused "big cloud" of "really abusing the license and privilege [of open source], by not giving back to the community." ZDNet reports: Even as MariaDB grows by leaps and bounds in enterprise computing at Oracle's expense, Howard sees Oracle and Amazon fighting against it. "Oracle as the example of on-premise lock-in and Amazon being the example of cloud lock-in. You could interchange the names, you can honestly say now that Amazon should just be called Oracle Prime...."

In the first keynote, Austin Rutherford, MariaDB's VP of Customer Success, showed the result of a HammerDB benchmark on AWS EC2... In these tests, AWS's default MariaDB instances did poorly, while AWS homebrew Aurora, which is built on top of MySQL, consistently beat them. The top-performing database management system of all was MariaDB Managed Services on AWS. "My first reaction when I looked at the benchmarks," said Howard, was "maybe there's incompetence going on. Maybe they just don't know how to optimize a DBMS." He observed that one MariaDB customer, one of the biggest retail drug companies in the world, had told MariaDB that "Amazon offers the most vanilla MariaDB around. There's nothing enterprise about it. We could just install MariaDB from source on EC2 and do as well."

He then "began to wonder, Is there something that they're deliberately crippling?" Howard wouldn't go so far as to say AWS is consciously doing a poor job of implementing its MariaDB instances. Howard did say, "And then it became clear that, however, you want to articulate this, there is something not kosher happening." Howard doesn't have much against AWS promoting its own brands... But, if AWS's going out of its way to make a rival service look inferior to its own, well, Howard's not happy about that.

ZDNet adds that "it's also quite possible that unoptimized generic MariaDB instance will simply lag behind AWS-optimized Aurora.

"That said, even in this most innocent take on the benchmark results, cloud customers would be wise to take into consideration that cloud instances of any specific software service may not be created equal."

17 of 200 comments (clear)

  1. Does anyone have a car analogy? by Anonymous Coward · · Score: 3, Funny

    I'm not comprehending enough of it.

    1. Re:Does anyone have a car analogy? by guruevi · · Score: 4, Informative

      Amazon basically offers 3 or 4 versions of the same car going from "you rent and maintain it yourself" to "you rent and we maintain and provide a driver for you". However it seems that if you bring your own mechanic and driver, no matter how skillful they are, their drivers and mechanics get consistently and measurably better performance out of the same car depending on the amount of money you pay to them even though they're all supposedly the same cars with the same specs.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
  2. Aurora performance is awful, too by shatteredsilicon · · Score: 5, Interesting

    I've consistently seen Aurora MySQL performance worse than RDS MySQL on writes, and overall, a carefully tuned (in a way you can't tune RDS or Aurora due to lack of access) MariaDB instance on EC2 will utterly annihilate Aurora and RDS on overall performance, for same instance sizes. Of course, a bare metal setup of the same size (same CPU cores, same RAM amount) will annihilate the EC2 instance on performance and at about half of the TCO over three years, but nobody seems to care about that these days.

    1. Re:Aurora performance is awful, too by whoever57 · · Score: 3, Interesting

      Fear of not being able to scale seems like the #1 concern in SV these days,

      As well as scaling issues, what moving to EC2, Google Cloud or other solutions gets you is a possible reduction in system admin costs.

      Of course, there is a minimum: if you only have one system admin, you probably can't reduce your system admin costs.

      --
      The real "Libtards" are the Libertarians!
    2. Re:Aurora performance is awful, too by Antique+Geekmeister · · Score: 3, Insightful

      A key factor is "possible" there. When your original sys-admin tasks have never been automated or kept in source control, the costs of shifting to a managed environment are startling. Decades of technical debt are often due in a very short period. I've particularly run into this with clients or partners who insist on optimizing their own kernels.

    3. Re:Aurora performance is awful, too by sfcat · · Score: 3, Interesting

      Fear of not being able to scale seems like the #1 concern in SV these days, but I swear to you for the average startup there are many, many more important problems you have to solve first.

      Exactly. And even if they don't have scaling problems, since all the *cool* kids are working on scale issues so should they. At company I worked for recently, one that you have probably heard of and probably has your data, at peak they handle about ~12000 web requests a minute...not a second, a minute. That's 200/second, on a 50 server array. That's 4 requests a second per machine...4...not 4000, or 400...as in my phone could do it without me noticing a slowdown in performance...4. So of course they spent gobs of money moving from their custom and very modern data centers with high uptime to GCE with terrible performance, just so they could "scale". Remember, 4 requests/machine/second is the max they had to handle before. Maybe 10% of the 600 engineers they had understood just how silly this all was. But the CTO, who started as a PHP programmer at the company when it was first starting, didn't understand any of this and just let his "professional" managers run everything into the ground. Its absurd really....the software industry is now a parody of itself...

      --
      "Those that start by burning books, will end by burning men."
    4. Re:Aurora performance is awful, too by phantomfive · · Score: 3, Interesting

      Recently I saw a company with three different nosql databases (and a relational database for slower things). This was to support fewer than 1,000 users. I showed them the Amazon "How to scale to 10million users" video (it's all over youtube), and sent them a summary of the bullet points (at around 1,000 users, we should consider getting off sqlite3. By 500,000 users, we need to have performance monitoring in place). That gave the non-technical people a road-map idea of priorities, and linking to Amazon gave it authority, even if they didn't actually watch it.

      --
      "First they came for the slanderers and i said nothing."
  3. Open source by Kohath · · Score: 4, Insightful

    These guys keep saying "open" and then they keep complaining about what others do with the source. Open means you don't get to control what other people do.

    1. Re:Open source by ConfusedVorlon · · Score: 4, Interesting

      That's hardly fair; For example; GPL is open source, but explicitly designed so that people who use it are under certain circumstances required to contribute back to it.

      The way the GPL is written; Cloud providers like Amazon don't have to contribute back to the project - but that's probably not what people wanted when they came up with the GPL.

      e.g. it's probably a legal bug, not a legal feature

      there are a bunch of different licences, I'm just using GPL as an example here.

    2. Re:Open source by Wycliffe · · Score: 4, Insightful

      Open means you don't get to control what other people do.

      You're wrong. Pretty much every open source software out there has an actual license attached which controls what people can do. One of the more common, GPL, was designed so that anyone can use it but if you sold a derivative that you have to open source the derivative too. This worked well when people were primarily selling software. The problem is that now places like google and amazon are selling services not software and as their derivatives are technically not being sold, they are not required to release the source to them. The GPL probably needs to be updated to include SaaS or at least IaaS but this is easier said than done because companies like Netflix and many other companies are also SaaS and also likely use custom GPL software that isn't exposed at all to the public. The goal of the GPL isn't "if you make money we want some of it" but rather "If you make improvements, you need to open source them so we can back port them". The GPL is basically saying "No Closed Source Forks". By that definition, Google, Amazon, and are plenty of others are in clear violation. The simplest solution is probably to rewrite the GPL explicitly so that it does say "No Closed Source Forks" and make it a requirement that all Forks are publicly available on something like github.

    3. Re:Open source by Vairon · · Score: 3, Informative

      Nowhere within the GPLv2 license used by MariaDB does it discuss, require or suggest contributing back to the original authors. Please take a few minutes to read or re-read the GPLv2 license. It will only take you a few minutes. Even if you think you've read it before; read it again. https://mariadb.com/kb/en/libr...

      The license only covers copying, distribution and modification. It makes this explicitly clear. The essence of the license is that you have the right to use, modify and distribute the software. If you distribute the software or derivative works of the software then you must bestow the same rights on those for whom you distribute the software to.

  4. If MariaDB Cared by phantomfive · · Score: 3, Insightful

    If MariaDB cared they should have used the AGPL. This has been an issue with open source for a long time now. Solutions are available, and you need to think before using the license.

    1) BSD - if you want your code to be used as many places as possible (even if you don't know about it)

    2) GPL - If you want to get paid when people use your code, either by keeping it free (redistribution/returning modifications), or by dual-licensing.

    3) AGPL - When you want to close the loophole here.

    And we can also add that the GPL3 closes the tivo and patent loopholes. Decide what you want, and choose the right license, otherwise you'll end up whining like Michael Howard.

    --
    "First they came for the slanderers and i said nothing."
  5. Re:I don't see problem here by phantomfive · · Score: 4, Insightful

    They aren't following the spirit of the GPL. They are being anti-social: taking from the labors of others, and not contributing back.

    There is no law against being anti-social, so they are free to do it.

    --
    "First they came for the slanderers and i said nothing."
  6. Re:Open Source does not require anyone to give bac by Wycliffe · · Score: 4, Informative

    Bascially, all your "customers" are required to do is share the source if they share binaries (in the case of the GPL 2.0) or not remove the license information (in the case of BSD-like licenses). If you can't live with that, don't publish under those licenses.

    The problem is that places like Amazon *ARE* "sharing the binary" as a service but then not sharing the modified source. The GPL was written when the primary way of sharing software was via binaries not services.

  7. Re:AWS customers by jtara · · Score: 4, Insightful

    It is the easy choice for management, because "everybody uses AWS".

    I've had to constantly defend my decision to use IBM Cloud as backend for an educational app. Because "everybody else" uses AWS. And this is in a primarily academic setting and background (spinoff from a project originally developed at a major U.S. university). We faced some issues with learning curve and the fact that you can't easily find consultants with IBM Cloud experience, and the "everybody" argument came up. It was eventually resolved, we got over the learning curve, and IBM has great support if you are willing to pony-up a modest $200/month for support.

    It boggles my mind that so many small/medium/large businesses in retail, wholesale, transportation, distribution, etc. are trusting their data and IT to and funding a company that is out to put them out of business. AWS is the ONLY real money-maker at Amazon. Their online retail operation is FINALLY making a 2% profit!

    IBM Cloud and Microsoft Azure are the RATIONAL choices right now if you want to use "big cloud" for critical infrastructure. We did not go with Azure because we do not have a Windows-based infrastructure, not into ASP, etc. etc. Though I realize that Azure has more Linux servers than Windows and offers the same open-source Linux-based solutions as the other cloud services. I think Azure would be a FINE choice for any company that is already bought-in to the Microsoft infrastructure, as they offer many unique services that would allow companies with in-house Windows-based server to move some or all to the cloud.

    Neither IBM nor Microsoft is interested in putting your retail business out of business.

  8. Re:Agree by jtara · · Score: 3, Insightful

    The open source community is founded by a group of volunteers. They choose, of their own free will, to create stuff without pay and give it away to the rest of the world.

    That's a naive statement.

    FOUNDED... yes... in some cases.

    But on an ongoing basis, most big/useful open source projects are funded primarily by corporate sponsors, who contribute money, talent, or both. Many companies contribute in-kind services, by assigning personnel either part or full-time to open-source projects.

    Another similar funding model is having a corporate parent that does consulting, hand-holding, hosting, etc. while opening the source for all. Yet another is the spin-off project that a parent organization needs for their own purposes, but is unrelated to their primary business. By open-sourcing, they get extra eyes on the project to find bugs, round-out capabilities, discover new use cases, etc.

    FEW important open-source projects are purely or even primarily volunteer indie projects!

    Unfortunately, this means that open source projects often have to kowtow to their corporate sponsors, and can suffer a sudden loss of talent and viability when they are "cut off" by a corporate sponsor.

    A good example of this is jQuery Mobile, which the jQuery Foundation still refuses to declare dead. Adobe pulled the plug years ago, it is Dead, Jim! A distant memory in the rearview mirror, but a ghost repo and ghost website remains, sitting there snagging unwitting third-world developers who think that it is still A Thing.

  9. Amazon's RDS storage is intentionally crippled. by rMortyH · · Score: 4, Interesting

    Amazon's RDS offerings are really convenient, from the perspective of making snapshots and setting up replication. But, I have never been able to push their default 'SSD' storage past 60MB/s. (PostgreSQL and Mysql) That's terrible. That's less than USB 2, and even some SD cards can do that! Our on-prem can do 180MB/s on spinning rust and around 550MB/s on (obsolete) SATA SSD. If you want anything better on RDS you have to REALLY pay a premium for IOPs and transfer, or pay a premium for way more ram and a ton of caching, in addition to external caching in the rest of your stack. I have not used Aurora on RDS, so I don't have a comparison, but I have my suspicions. It would be pretty easy to just give you a few more MB/s and make it look a whole lot better. Luckily in our case we could optimize things enough that storage performance didn't matter too much. But RDS storage performance is so pitiful that it's seriously worth considering putting your DB on a bare metal box somewhere with NVME storage and just put up with the network latency and get 50 times the storage performance (and more ram and cpu while you're at it ) at a fraction of the price.