Slashdot Mirror
Slimmed Down MySQL Offshoot Drizzle is Built For the Web
Incon writes "Builder AU reports that Brian Aker, MySQL's director of architecture, has unveiled Drizzle, a database project aimed at powering websites with massive concurrency as well as trimming superfluous functionality from MySQL. Drizzle will have a micro-kernel architecture with code being removed from the Drizzle core and moved through interfaces into modules. Aker has already selected particular functionality for removal: modes, views, triggers, prepared statements, stored procedures, query cache, data conversion inserts, access control lists and some data types."
I'm guessing you're going for a "+5 Funny" here, right?
Reading the feature list, it sounds like they've now got a slow clone of SQLite with a more restrictive license. Good to see MySQL are innovating again. I think I preferred it when they had a buggy, feature-incomplete clone of PostgreSQL with a more restrictive license...
I am TheRaven on Soylent News
There's nothing wrong with MySQL. It serves its purpose.
I disagree, but lets not start that discussion just yet.
And there's nothing wrong, necessarily, with sacrificing ACID compliance for speed.
Nowhere in my post did I even mention ACID. That's a different issue. Equally important, but different.
The goal for those like you and I is to be sure these younger Dev's are using it appropriately.
Assuming we agree on the definition of "appropriately."
For example, during a code review if you see a developer doing a multi-table insert where he's checking for an error and doing a manual roll-back of the insert, that's a perfect time to demonstrate transactions as a way to save the developer time.
Which drizzle wouldn't have.
In many ways, the sheer popularity of MySQL gives it legitimacy.
I find any argument based on "popularity" fundamentally flawed. Windows is very popular. So is velvita "cheese."
Of course, if you're one that thinks MySQL et al have no place in a production environment, maybe they SHOULDN'T be listening to you...
Ahh, the defense of the indefensible. MySQL is a bad system and drizzle will just be worse. I was not talking about "transactions" or data integrity in my first post. That is a WHOLE different stupidity in MySQL. I was talking about keeping "data logic" close to the data and out of the application.
Little known fact: MySQL, when using isam -- and everyone uses isam, locks out table updates during READS. MySQL is woefully inadequate is in query optimization. So, while your team is doing simple SQL select and doing further processing on the data in the application because MySQL can't or your team doesn't want to do it in the database, you are locking out writes and updates. More over, the extra data you are retrieving from the database, because you are doing additional processing and selection in the application, means you are performing more I/O on the database server, which adds to the I/O bottleneck.
Anyone who argues that MySQL has a place a real enterprise seriously lacks the experience and/or education to make such a statement. MySQL is insanely bad at being a SQL database.
But hey, if you think it is worth while, I'll be willing to debate you. I'll even let you start. Imagine you are a CTO and you are choosing a database for your web site, please write an executive summary explaining your choice and the criteria for your selection, why MySQL was a better choice than PostgreSQL, DB2, Oracle, SQLite, or Sybase. Then create a list of features and limitations of the various systems and indicate for each feature why MySQL was better or that it did not matter.
I have done this many times, MySQL has never been the right choice.
Imagine this: Apache announces, that it will remove some of its features, like for example mod-php, mod-perl, mod-rewrite.. moved to modules! Gone - forever!