Comments on: The State of MySQL http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/ because technology is just another ecosystem Tue, 02 Dec 2008 05:11:41 +0000 http://wordpress.org/?v=2.6.3 By: To Postgres or MySQL that is the question. « Technophilia http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-381818 To Postgres or MySQL that is the question. « Technophilia Sat, 10 May 2008 14:31:42 +0000 http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-381818 [...] I read this post on the State of MySQL by stephen o’grady of redmonk and this comment caught my attention [...] [...] I read this post on the State of MySQL by stephen o’grady of redmonk and this comment caught my attention [...]

]]> By: Full Table Scan http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-366203 Full Table Scan Tue, 22 Apr 2008 22:13:27 +0000 http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-366203 <strong>The Value of MySQL Storage Engines...</strong> Or, The World May Be Coming to an End Something very disturbing happened yesterday. I started liking the idea of MySQL storage engines. It happened after reading the second comment of this post. In retrospect this article had a lot of influence... The Value of MySQL Storage Engines…

Or, The World May Be Coming to an End

Something very disturbing happened yesterday. I started liking the idea of MySQL storage engines.

It happened after reading the second comment of this post. In retrospect this article had a lot of influence…

]]> By: MySQL Storage Engine http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-363869 MySQL Storage Engine Sat, 19 Apr 2008 17:23:21 +0000 http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-363869 I was at the MySQL conference and spoke with a product manager from DB2. He was shocked at the fact that there were so many storage engines built for MySQL and that they were truly innovating. In the closed software world you don't get that. Ironically, my friend started ScaleDB (a pluggable storage engine for MySQL) after years of trying to get the closed source guys to adopt (or even try) his revolutionary indexing. Now with MySQL he can build his own storage engine, incorporate his indexing and he is in control of his destiny. He doesn't have to spend years begging the big guys to try his solution, he just shows them how much better it is. I'm confident that, with this sort of innovation around the core of MySQL and the mass adoption of MySQL, we will soon see it addressing markets now served only by the large commercial databases. Then the market will get really interesting. I was at the MySQL conference and spoke with a product manager from DB2. He was shocked at the fact that there were so many storage engines built for MySQL and that they were truly innovating. In the closed software world you don’t get that.

Ironically, my friend started ScaleDB (a pluggable storage engine for MySQL) after years of trying to get the closed source guys to adopt (or even try) his revolutionary indexing. Now with MySQL he can build his own storage engine, incorporate his indexing and he is in control of his destiny. He doesn’t have to spend years begging the big guys to try his solution, he just shows them how much better it is.

I’m confident that, with this sort of innovation around the core of MySQL and the mass adoption of MySQL, we will soon see it addressing markets now served only by the large commercial databases. Then the market will get really interesting.

]]> By: Jay http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-363403 Jay Fri, 18 Apr 2008 21:29:10 +0000 http://redmonk.com/sogrady/2008/04/17/the-state-of-mysql/#comment-363403 "Not because it’s a uniquely differentiated product; it is, ultimately, another relational database." But MySQL is a highly extensible relational database (dramatically so in 5.1). It's not just about custom data types and user defined functions. The 'plugin your own MySQL storage engine for production use' movement is both small and somewhat secretive, but that kind of functionality doesn't have any competition that I know of. (Not to mention some of the other ways to extend MySQL). Most examples of custom storage engines are rather pointless and only serve as education or particularly geeky showmanship. ("Really, MySQL front-end, Google spreadsheets back-end? I'm so...proud...for you"). Of course, the S3 backend for mysql (http://fallenpegasus.com/code/mysql-awss3/) -- especially since they now have persistent storage for s3 -- has more than a handful of interesting use cases. In high-transaction database environments, a lot of performance problems resolve to disk I/O. Having the ability to write a DB storage engine that knows about your specific data layout on disk is an appealing capability -- even if you don't use it. “Not because it’s a uniquely differentiated product; it is, ultimately, another relational database.”

But MySQL is a highly extensible relational database (dramatically so in 5.1). It’s not just about custom data types and user defined functions. The ‘plugin your own MySQL storage engine for production use’ movement is both small and somewhat secretive, but that kind of functionality doesn’t have any competition that I know of. (Not to mention some of the other ways to extend MySQL).

Most examples of custom storage engines are rather pointless and only serve as education or particularly geeky showmanship. (”Really, MySQL front-end, Google spreadsheets back-end? I’m so…proud…for you”). Of course, the S3 backend for mysql (http://fallenpegasus.com/code/mysql-awss3/) — especially since they now have persistent storage for s3 — has more than a handful of interesting use cases.

In high-transaction database environments, a lot of performance problems resolve to disk I/O. Having the ability to write a DB storage engine that knows about your specific data layout on disk is an appealing capability — even if you don’t use it.

]]>