tag:blogger.com,1999:blog-768233104244702633.post2705582010323017797..comments2023-11-16T03:16:54.746-08:00Comments on The Scale-Out Blog: Contemplating the MySQL DiasporaRobert Hodgeshttp://www.blogger.com/profile/05379726998057344092noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-768233104244702633.post-89947954676491917982009-04-10T10:07:00.000-07:002009-04-10T10:07:00.000-07:00Hi Adrian, Bummer--I'm going to miss this. It's a...Hi Adrian, <BR/><BR/>Bummer--I'm going to miss this. It's also an excellent time for Spring skiing on Mt. Baker. :( Have fun and give my regards to Josh Drake. <BR/><BR/>Cheers, RobertRobert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-74945831039204582382009-04-10T09:26:00.000-07:002009-04-10T09:26:00.000-07:00If you are interested in the future of databases t...If you are interested in the future of databases then might I suggest you attend LinuxFest NW (www.linuxfestnorthwest.org/).<BR/>See the blog(//lfnw.wordpress.com/) for information on PgDay, as well as Monty Widenius's talk. His description of his talk:<BR/>"MariaDB (MySQL branch) and Maria Engine (transactional storage engine for MySQL. The presentation will be an open environment, where the audience helps to decide the topics...and the discussion is open for debate."<BR/><BR/>Sounds like a continuation of this discussion.Adrian Klavernoreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-9546694978740167372009-04-06T12:17:00.000-07:002009-04-06T12:17:00.000-07:00Hi Brian!I'm completely with you on the notion of ...Hi Brian!<BR/><BR/>I'm completely with you on the notion of a database renaissance. There's another way of reading the economics--it now makes the experiments viable. There is room for at least 3 variants of MySQL, maybe more. Adrian counted two, but the market is really large. <BR/><BR/>That means there is also another perfectly reasonable conclusion to the end of the article: It's going to be really fun working on databases for quite some time. <BR/><BR/>Cheers, RobertRobert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-91184626844146426372009-04-06T12:06:00.000-07:002009-04-06T12:06:00.000-07:00Hi!Personally I think that we are hitting a period...Hi!<BR/><BR/>Personally I think that we are hitting a period of renaissance in the code base. This really is the first time that so many individuals have been asking the question of "what if". I believe we are just at the starting point for what could be a period of reflection on what has been created and what we need to see done going forward.<BR/><BR/>Cheers,<BR/> -BrianAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-40325255223932569352009-04-06T06:53:00.000-07:002009-04-06T06:53:00.000-07:00My guess is at some point they are going to have t...My guess is at some point they are going to have to make a choice, roll back to the 4.X model or commit fully to the 5.X model. While the ability to fork Open Source projects is great, it also can become a burden. Right now we are seeing a MySQL diaspora, but at some point the forks are going to coalesce. I still hold that it will be around the two usage patterns I described earlier. Those who choose to buck that are going to be left out in the cold.Adrian Klavernoreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-80462125203393066112009-04-05T19:44:00.000-07:002009-04-05T19:44:00.000-07:00Your comment seems to miss a key constituency, nam...Your comment seems to miss a key constituency, namely people who are running reasonably vanilla applications on MySQL 5.0 to 5.1 releases and just want bugs fixed. There are at least three forks now aimed at those users.Robert Hodgeshttps://www.blogger.com/profile/05379726998057344092noreply@blogger.comtag:blogger.com,1999:blog-768233104244702633.post-29233006979381603432009-04-03T18:13:00.000-07:002009-04-03T18:13:00.000-07:00The basic problem is different expectations. MySQL...The basic problem is different expectations. MySQL grew up as the database for web applications, where data is treated as flat files. MySQL 5.X is an attempt to bring the full power of the relational model to bear and make MySQL enterprise material. This is what Sun paid 1 Billion for. What it got was something less than that, see Monty's comments. Now there is fork in the user base between those that want the simple model of the 4.X series and those that want the enterprise features promised in the 5.X series. What we are seeing is the race to see who can be the first to satisfy the respective usage patterns.Adrian Klavernoreply@blogger.com