NoSQL and NewSQL database technologies pose a long-term competitive threat to MySQL’s position as the default database for Web applications, according to a new report published by 451 Research.
The report, MySQL vs. NoSQL and NewSQL: 2011-2015, examines the competitive dynamic between MySQL and the emerging NoSQL non-relational, and NewSQL relational database technologies.
It concludes that while the current impact of NoSQL and NewSQL database technologies on MySQL is minimal, they pose a long-term competitive threat due to their adoption for new development projects. The report includes market sizing and growth estimates, with the key findings as follows:
• NoSQL software vendors generated revenue* of $20m in 2011. NoSQL software revenue is expected to rapidly grow at a CAGR of 82% to reach $215m by 2015.
• NewSQL software vendors generated revenue* of $12m in 2011 (of which $9m is also considered MySQL ecosystem revenue). NewSQL revenue is also expected to grow rapidly at a CAGR of 75% to reach $112m by 2015 (including $56m in MySQL ecosystem revenue).
• The MySQL support ecosystem generated revenue* of $171m in 2011 (including $9m from NewSQL technologies). MySQL ecosystem revenue is expected to grow at a CAGR of 40% to reach $664m by 2015 (including $56m in NewSQL revenue).
“The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a strong vendor committed to the core product, and a wealth of alternative and complementary products and services on offer to maintain competitive pressure on Oracle,” commented report author Matthew Aslett, research manager, data management and analytics, 451 Research.
“However, the options for MySQL users have never been greater, and there is a significant element of the MySQL user base that is ready and willing to look elsewhere for alternatives,”
As well as revenue and growth estimates, the report also includes a survey of over 200 database administrators, developers, engineers and managers. The survey findings include:
• While the majority of MySQL users continue to use MySQL where appropriate, the use of MySQL is expected to decline from 80.5% of survey respondents today to 62.4% by 2014 and just 54.1% by 2017.
• Despite the emergence of NoSQL and NewSQL database products, the most common direct replacement for MySQL among survey respondents today is PostgreSQL, which is also the focus of a recent burst of commercial activity.
• While 49% of those survey respondents abandoning MySQL planned on retaining or adopting NoSQL databases, only 12.7% of MySQL abandoners said they had actually deployed NoSQL databases as a direct replacement for MySQL.
“While there have been some high profile example of users migrating from MySQL to NoSQL database, the huge size of MySQL installed base means that these projects are comparatively rare,” commented Aslett.
The report describes how NoSQL database technologies are largely being adopted for new projects that require additional scalability, performance, relaxed consistency and agility, while NewSQL database technologies are, at this stage, largely being adopted to improve the performance and scalability of existing databases, particularly MySQL.
“NoSQL and NewSQL have not made a significant impact on the MySQL installed base at this stage but MySQL is no longer the de facto standard for new application development projects,” said Aslett. “As a result, NoSQL and NewSQL pose a significant long-term competitive threat to MySQL’s dominance.”
MySQL vs. NoSQL and NewSQL: 2011-2015 is now available to existing 451 Research subscribers. Non-clients can apply for trial access to 451 Research’s content.
*451 Research’s analysis of MySQL, NoSQL and NewSQL revenue is based on a bottom-up analysis of each participating vendor’s current revenue and growth expectations, and includes software license and subscription support revenue only. Revenue line items not included in these figures include hardware associated with the delivery of these services, revenue related to applications deployed on these databases, traditional hosting services, or systems integration performed by the vendors or other third parties.
The revenue estimates do not take into account unpaid usage of open source licensed MySQL, NoSQL and NewSQL software, and therefore represent only a fraction of the total addressable market. Based on the above revenue figures and other analysis, 451 Research estimates that the total value of the MySQL ecosystem in terms of ‘displaced’ proprietary software might equate to $1.7bn in 2011, while the NoSQL market had a displaced value of $195.7m and the NewSQL sector a displaced value of $99.4m.
7 comments ↓
[…] and continuing to foster its community. As Matthew Aslett, research manager with 451 Research, notes: “The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a […]
[…] and continuing to foster its community. As Matthew Aslett, research manager with 451 Research, notes: “The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a […]
[…] and continuing to foster its community. As Matthew Aslett, research manager with 451 Research, notes: “The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a […]
[…] and continuing to foster its community. As Matthew Aslett, research manager with 451 Research, notes: “The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a […]
[…] and continuing to foster its community. As Matthew Aslett, research manager with 451 Research, notes: “The MySQL ecosystem is now arguably more healthy and vibrant than it has ever been, with a […]
I am not sure how you got the figure of $20 m revenue generation from NoSQL databases. Don’t you consider players like MarkLogic in this group?
Thanks for the question. Our methodology is to analyse all the players individually in relation to their current licensing/support revenue and growth prospects. It does not include associated hardware and services. That way we are very confident that the figure is based on actual revenue, rather than an estimated whole. In this iteration we did not include MarkLogic as we have not previously considered them to be in the original NoSQL category of databases.
I am aware of the arguments that they should be, and do know describe themselves as a NoSQL database vendor. We will reconsider this when we update the estimates.
Thanks
Matt