PlanetMysql.ru — информация о СУБД MySQL

Previously, I’ve called out years for non-desktop Linux in 2008, Linux in both the low and high-ends of the market in 2009, ‘hidden’ Linux in 2010 and last year, cloud computing in 2011. For 2012, I see continued growth, prevalence, innovation and impact from Linux, thus leading to a 2012 that is dominated by Linux.

I expect to see nothing but continued strength for Linux and open source in cloud computing in 2012. The cloud continues to be the biggest disruptor and opportunity for Linux providers. 2012 got off to an interesting start with Microsoft’s efforts to support for Linux on Azure, which highlights just how pervasive Linux has become in cloud computing. As detail in our special report on The Changing Linux Landscape, we also expect Linux to continue to be the basis for most offerings in IaaS and particularly PaaS, which is burgeoning across open source languages and frameworks as well as verticals and enterprise customers. Its popularity among enterprise and other developers will also bolster Linux and open source software in 2012.

We can certainly expect to see Linux continue its domination in supercomputing and the Top 500 Supercomputer List, where Linux continues to grow its share above 90% while others, such as Microsoft, Apple and BSD, fall off of the list.

I also expect Linux will grow its presence and impact on the wider, more mainstream server market, where Red Hat and SUSE continue to benefit from Unix migration, particularly from Solaris. Our analysis with survey data from 451 Research division TheInfoPro shows server spending for databases and data warehousing favoring Red Hat with Linux over Oracle with either Linux or Solaris. Out of more than 165 server professionals interviewed by TIP, 67% are planning to spend more with Red Hat on database/data-warehousing, and only 6% plan to spend less. The positive figures for Red Hat mirror negative spending intentions for Oracle, with 55% planning to spend less and only 9% planning to spend more. Spending continues to decline strongly for all of the primary Unix providers in the study, which in addition to Oracle includes IBM and Hewlett-Packard.

We may also see further expansion for Red Hat, which may be eyeing key acquisitions, and other Linux and open source vendors as they continue building their channels and wade more into midmarket and SMB customers.

In smartphones and mobile software, I also expect Linux will do quite well in 2012 with continued Android strength, diminished FUD and possibly an open source boost from a newly-open sourced WebOS. We also see Ubuntu arriving on the mobile and converged device scene, including ‘concept’ appearance at CES.

We’re also likely to see Linux in automobiles, health care and other electronics even more in 2012, though you may never hear Linux or open source. Don’t be fooled though, Linux is expanding its already impressive, wide presence and 2012 looks to be another year of significant gains.

PlanetMySQL Voting: Vote UP / Vote DOWN

I’ve always been a big fan of having a customized .bashrc file. The one I distribute to all of my servers has aliases for quick commands to save me time on the command line, functions that get work done when aliases are too simplistic, reporting for the server for each cli login, and of course a formatted and colored prompt (for terms that support colors). I also change certain aspects and commands based on the operating system since I’m not always on a redhat box or linux at all. Here’s my bashrc file – maybe you have some fun additions that you’d like to share. What saves you time on the command line?

PlanetMySQL Voting: Vote UP / Vote DOWN

In this latest release I’ve added a basic MySQL connection pool to the benchmarking script which improves the method in which connections to MySQL are handled and reused. In addition, there have been some optimizations made to the thread handler functions for better debug reporting. Download the latest release now and see how your MySQL server performs against the rest of the community! Download here: download page.

PlanetMySQL Voting: Vote UP / Vote DOWN

So far the benchmarking script supports Linux, FreeBSD, and OSX. I’m installing virtual machines today to get ready for development on the next OS that the community wants to have supported. Vote today for your choice. Development will begin Friday 2010-09-03.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.
PlanetMySQL Voting: Vote UP / Vote DOWN

I’m pleased to announce the first release of Kontrollcomm – “The Server Command Automation Interface” is a web-based application that automates remote command execution on linux and unix based servers. There are three main areas of the application: Hosts, Templates, and Commands. The use is very simple: all of your hosts are setup in the [...]
PlanetMySQL Voting: Vote UP / Vote DOWN

We’re continuing to see signs that the dominant GPL open source license may be fading from favor among commercial open source software players. The latest move away from the GPL comes from content management software vendor Alfresco, which is moving to the LGPL after originally releasing its code under the GPL three years ago. The reasoning for the shift, according to Alfresco CEO John Newton, is the company sees greater opportunity beyond being a software application, particularly given the emergence of the Content Management Interoperability Services standard. Alfresco won mostly praise for its move, and it does make sense given where open source is going these days.

I believe the emerging trend away from GPL and toward more permissive, mixable licenses such as LGPL or Apache reflects the broadening out of open source software not only throughout the enterprise IT software stack, but also throughout uses beyond individual applications, frameworks and systems. More and more open source software vendors are pursuing opportunities in embedded use or OEM deals whereby open source software often must sit alongside or even inside of proprietary code and products. Similar to what we’ve seen in the mobile space — where open source software and development are more prominent than ever, but end products with accessible code are not — open source is broadening out, but it is doing so in many cases by integrating with proprietary code.

We also see some debate about the community and commercial ups and downs of GPL as organizations contemplate the balance of the two and the best way to achieve commercial success with open source software. As Matt highlights, we are seeing a choice of non-GPL licensing in order to more effectively foster community and third-party involvement, but we also continue to see GPL as a top choice to similarly build community.

While the debate about community versus commercial benefit may not necessarily be prompting movement away from GPL, I believe another recent action may indeed do so. The latest series of GPL lawsuits are aimed at raising awareness, profile and legitimacy for open source software. While those bringing the suits — primarily the Software Freedom Law Center — have exhibited a reasonable approach and settled with past lawsuit targets, these suits and publicity may still serve to steer organizations making the choice to other licenses, including the LGPL, BSD, Apache and the Eclipse Public License.

Another factor is the GPL thumping that took place during the SaveMySQL campaign as the European Commission contemplated Oracle’s proposed (and now closed) acquisition of Sun Microsystems and the open source MySQL. I voiced my concern that the SaveMySQL campaign might jeopardize or de-value open source software projects and pieces in M&A, but I believe I’m actually in agreement with SaveMySQL leader Monty Widenius that the deal and process may end up tarnishing the GPL and its reputation in the enterprise.

As stated above, much of the movement we’re seeing away from the GPL has to do with the desire and opportunity to place open source software alongside, within, on top of or otherwise with proprietary software. Non-GPL open source licenses are also more flexible in terms of integrating and bundling with other open source software licensed under other, non-GPL licenses.

We anticipated this fade of GPL as covered in our report, The Myth of Open Source License Proliferation. Given its clout, durability and continued popularity in commercial open source (and with help from continued growth of GPL-licensed Linux) we believe the GPL will endure as a top open source license. However, given their flexibility and the ability to combine with other code, we see a number of other challengers — Apache, BSD, EPL and LGPL — rising while GPL dominance wanes. We’re also watching to see whether the AGPLv3 for networked software will provide new life for GPL-style licensing and community building in emerging virtualized, SaaS and cloud computing environments.

PlanetMySQL Voting: Vote UP / Vote DOWN

Having been a free software user and supporter for many years, I am disheartened by some of the comments made in the MySQL/Oracle debate regarding the GNU Public License (GPL) and other licenses. There is much throwing around of misconceptions and untruths about licenses and their differences. In this blog, I shall take on some of the bigger misconceptions.

While Linux is indeed distributed under the GPL, as is MySQL, Linux has an exception that allows anyone to run any kind of applications (including closed source applications) on top of Linux.

Monty says: Help keep the Internet free

There is nothing in the GPL that forbids running closed source applications on top of GPL-licensed software. The only thing that GPL has in this regard is that if you make changes to GPL-licensed software and re-distribute it as a binary, then you must make the modified source code available. This is the reason why commercial Linux distributions make available their source code, either online (as Red Hat does) or on the demand of those who purchase copies (à la SUSE). It is also the reason why there are many commercial software products running on Linux, such as the Oracle Database Server, MATLAB, etc., etc.

I think that GPL is a great open source license, in many cases the best license. The GPL license ensures freedom of the code and at the same time gives the copyright holder a very strong control on the code and it’s ecosystem, especially it’s closed source customers.¹

Monty says: Help keep the Internet free

This is another contradiction. How does the GPL give the copyright owner strong control over its closed source customers? In fact, the rules of GPL mandate that any closed source customer is able to obtain a copy of the source code for their closed source version. Furthermore, that customer is then able to release the source code to anyone, and if they want to, sell their own version. So in fact, with the GPL there is no way to control their closed source customers.

Currently, anyone can take the MySQL source code and make changes to it, as Percona and Monty AB currently do. If, however, they decide to sell a closed source copy, they must also provide the source if asked to do so–as the GPL enforces.

Oracle should change the license of MySQL to a more permissive Open Source license that would ensure that if Oracle would try to kill MySQL, the community would be able to take over and rescue MySQL and develop it as a product that can be freely used by everyone.

Monty says: Help keep the Internet free

The fact that it is GPL-licensed means that anyone fork it and create their own version, as Percona and Monty AB have done, regardless of whether Oracle kills it or does not. So what would releasing MySQL under a more permissive Open Source license (such as the Apache Software License or the BSD license) give the community?

Nothing, I believe. It would give anyone the freedom to take MySQL, make changes to it, and sell it as a closed source product, without having to share the source. And that sounds to me like a much better way to control one’s closed source customers than the GPL.

So, a change of license would benefit only those who want to produce and sell a modified version of MySQL and sell it without the obligation to give away the source code.

1. I understand “closed source customer” to be mean one that has purchased a binary copy. back

PlanetMySQL Voting: Vote UP / Vote DOWN

Topics for this podcast:

*EC pauses Oracle-Sun over MySQL
* Open source licenses debated
* Red Hat growth opportunities and Summit roundup
* Reductive Labs seeking cloud role for Puppet software
* VMware-SpringSource analyzed

iTunes or direct download (26:04, 5.9 MB)

PlanetMySQL Voting: Vote UP / Vote DOWN

It appears that little MySQL has just become a disproportionally big player in the Oracle-Sun takeover deal…. article by Associated Press: EU probes Oracle’s bid to buy Sun notes:

EU Competition Commissioner Neelie Kroes said Thursday that regulators needed to examine the effect of a deal “when the world’s biggest proprietary database company proposes to take over the world’s leading open-source database company.”

Ah, Neelie Kroes. Dutch lady from the liberal (that’s seriously right-wing in NL, my American friends party, formerly minister for infrastructure in NL, long time ago.

So what can happen now? The EU can (and I’m skipping a few steps for brevity here) force the MySQL part of Sun to be auctioned separately, to allow the remainder of the detail to go through. One thing is fairly predictable, the price is probably not going to be $1 bln. As far as it wasn’t overpriced back then, a fair amount of talent and activity is not actually inside Sun any more. Less predictable, who might buy what is now there?

And on a side note, where will Drizzle fit… would be regarded as part of the MySQL bundle as it uses its IP for its foundation? If MySQL goes, and Drizzle stays, then Sun(/Oracle) will have a project for which it does not own the core IP. That can be perfectly fine, but that’s not what it’s been aiming for: Drizzle accepts contributions under BSD license, which means that the core IP owner (currently Sun) is actually able to dual-license it just like MySQL. Not saying that’s what it intends with Drizzle, but the arrangement currently makes Drizzle a potential net asset rather than merely a cool/useful project.

I think that both MySQL and Drizzle can survive without anyone in particular owning the core IP, just like no particular core IP owner would be able to kill the projects. There’s too much independent interest (not just intellectual but business/money) and activity, so it really doesn’t matter from that respect. But it’s just a whole lot of unheaval that, perhaps, we might be better off without.

In any case… who would have thought, that little database originally written by Monty in Helsinki, causing so much trouble

PlanetMySQL Voting: Vote UP / Vote DOWN

This is my assessment as a judge of the recently-held open source license debate held by the FOSS Learning Centre. We’ll have to begin with some qualifications and definitions, starting with the fact that there is no ‘best’ open source software license. Still, a star-studded open source software panel provided a lively, informative debate on the merits of some top open source licenses. For that, I congratulate and thank the panelists, Mike Milinkovich from the Eclipse Foundation arguing for the Eclipse Public License, Matt Asay of Alfresco arguing in favor of the GPL and David Maxwell from Coverity arguing for BSD. All three put forth some of the most important attributes and shortcomings of the three open source licenses, as well as other, related open source licenses. However, using a complex, proprietary formula awarding points for goodness and minuses for badness, I was able to deem a winner: Mike Milinkovich and the EPL. Perhaps fitting that the license that can best be described as the middle of the spectrum should be the winner. Here’s why:

Matt Asay kicked off the discussion, which became more of a debate as it developed, with a consistent message about GPL’s dominance among open source software projects, which is 70% or more based on most accounts (and considering GPLv2 and GPLv3). He also referred to monetization and the fact that GPL serves as the basis for successful support and services models, such as Red Hat. However, Matt did not initially mention the strategic and defensive benefits of GPL, which is often chosen because it mitigates the threat of a fork that someone can make proprietary. I was also hoping for him to address how GPL can deliver benefits of open source without having to share as in the spirit of the license, based on whether and how the software is distributed. Nevertheless, Matt made his most compelling arguments around the fact that GPL is the primary open source model and the license that developers understand and trust most. He furthered his argument later by agreeing EPL may be better for lawyers, but GPL is better for developers. Matt reinforced these ideas with his reference to large companies using GPL software, such as Google or TiVO, that gets it to vast numbers of users.

Mike Milinkovich spoke second with some background on EPL, its origin as a ‘legal document’ and how it links open source software to commercial products. He also hit on the fact that EPL covers patent rights, which is certainly important to vendors and developers. He later referred to the meaninglessness of Matt’s 70% GPL figure, based on the idea that software on repository is something different than software in use (where other licenses do have greater representation). However, our research indicates that the most popular open source licenses among hosted code are consistent with the most popular open source licenses among code in use, with GPL, BSD and EPL all in the top. Mike also referred to commercialization and money, which is certainly important to commercial open source, but did not give equal mention to community until later. Still, Mike earned back a point when he referred to monetization of open source software among traditional vendors and organizations beyond VC-funded, open source startups, where we are seeing significant growth for open source software. While I would have liked to have heard an argument in favor of EPL based on compatibility, Mike also made a good case for EPL in government — another consistent theme of the discussion — where code would belong to the public with commercial opportunity on top.

David Maxwell signaled a more rebuttal-type response and gave it in his arguments for the BSD license, which he introduced as the oldest license given its roots to Unix and the ’80s. David scored a point for simplicity and straightforwardness when he read the actual license, something his peers would’ve had a hard time doing. David did somewhat jump the gun, though, on rebutting with his counterpoints about GPL’s strict copyleft requirements, which he called ‘enforcement-based.’ Still, David recovered with an argument for BSD based on its emulation, which he credited for other popoular licenses such as the Apache Public License and Artistic License.

The debate portion was followed by some good discussion of business models, open core and proliferation with questions from the live and Web audiences. So why does my vote for the winner go to Mike and the EPL? While it was certainly close on my card and all three made compelling arguments, Mike and his portrayal of the EPL were the most realistic and pragmatic to today’s open source software in the enterprise. Communities, copyleft and the sharing that allows developers and projects to sustain effective, productive open source efforts must be balanced with commercial interests, endeavors and aspiration. Neither open source communities nor open source commercialization would be nearly as significant without one another, and Mike’s arguments and statements seemed most closely attuned to that.

Thanks again to the panelists, participants and FOSS Learning Centre for putting on the event. Please get involved in the discussion and watch the debate, comment here or elsewhere.

PlanetMySQL Voting: Vote UP / Vote DOWN