Entries from January 2013 ↓
January 30th, 2013 — Data management
Actian acquires Pervasive. ObjectRocket has liftoff. And more.
And that’s the data day. today.
January 28th, 2013 — Data management
Informatica’s revenue is in. Hortonworks joins OpenStack. And more.
And that’s the Data Day, today.
January 24th, 2013 — Data management
SAS. SAP. Actuate. Guavus. Cirro. ACID. And more.
And that’s the Data Day, today.
January 23rd, 2013 — Data management
We are very honoured to have been asked to give a “state of the MySQL” keynote presentation at the Percona Live MySQL Conference and Expo in April.
While this will not be in any way an official “state of the dolphin” presentation, I think it is fitting given the expansion of the MySQL ecosystem that the Percona Live event includes an independent perspective on the state of MySQL. The full title of the presentation – MySQL, YourSQL, NoSQL, NewSQL – the state of the MySQL ecosystem – reflects that.
We want to present an independent perspective on the health of the MySQL ecosystem in 2013, drawing on our research and analysis, as well as the views of the participants in that ecosystem.
You have a chance to directly influence the content of the presentation by taking part in our 2013 Database survey.
The aim of this survey is to identify trends in database usage, as well as changing attitudes to MySQL following its acquisition by Oracle, and the competitive dynamic between MySQL and other databases, including NoSQL and NewSQL technologies, as well as MariaDB, Percona Server and other MySQL variants.
There are just 15 questions to answer, spread over five pages, and the entire survey should take less than ten minutes to complete.
All individual responses are of course confidential. The results will be published as part of a major research report due during Q2.
The full report will be available to 451 Research clients, while the results of the survey will also be made freely available via the keynote presentation.
Thanks in advance for your participation. We’re looking forward to analyzing and presenting the results. Once again, you can find the the survey at http://bit.ly/451db13
January 22nd, 2013 — Data management
DataStax and VoltDB launch their version 3.0s. And more
And that’s the Data Day, today.
January 21st, 2013 — Data management
Next week at Cloud Expo Europe in London I’ll be giving a presentation – at 12.05 on January 29 to be precise – on the potential confluence of bog data and cloud computing.
Cloud computing is all about enabling frictionless adoption of low-cost, flexible compute and storage, while big data technologies such as Apache Hadoop enable low-cost, flexible data storage and processing. Hence many people seem to believe that cloud computing and big data have the potential to create a perfect storm of disruption.
However, 451 Research has been tracking the adoption of data management technologies on the cloud – and the lack of it – since relational databases became available on AWS in 2008, and the effect of the confluence of big data and the cloud would perhaps better be described as dead calm, rather than a perfect storm. Other than development and test environments, adoption has been limited.
In our presentation “Big Data and the Cloud: A Perfect Storm?” we will take a look at the factors that have restricted adoption of databases in the cloud to date, explain why we see the potential for cloud database growth in the coming years, and examine how the strategies of emerging Hadoop- and database-as-a-service providers are evolving to ensure that big data and the cloud combine to fulfil their potential to disruptive the IT landscape as we know it.
January 16th, 2013 — Data management
Funding for Ayasdi and Zettaset. NuoDB launches cloud database. And more
And that’s the Data Day, today.
January 15th, 2013 — Data management
As 2012 came to a close I tweeted
NuoDB has today kicked off that debate with the launch of its Cloud Data Management System and 12 rules for a 21st century cloud database.
NuoDB’s 12 rules appear pretty sound to me – in fact you could argue they are somewhat obvious. This is actually to NuoDB’s credit in my opinion, in that they haven’t simply listed 12 differentiating aspects of their product, but 12 broader requirements.
Either way, I believe that this is the right time to be debating what constitutes a “cloud database”. Database on the cloud are nothing new, but these are existing relational database products configured to run on the cloud.
In other words, they are databases on the cloud, not databases of the cloud. There is a significant difference between spinning up a relational database in a VMI on the cloud versus deploying a database designed to take advantage of, enable, and be part of, the cloud.
To me, a true cloud database would be one designed to take advantage of and enable elastic, distributed architecture. NuoDB is one of those, but it won’t be the only one. Many NoSQL databases could also make a claim, albeit not for SQL and ACID workloads.
This isn’t a matter of SQL versus NoSQL, however. We’ve seen companies building their own next-generation database platforms deploying NoSQL and SQL technologies alongside each other for different workload and consistency requirements. Where the SQL layer falls down is the inability of existing relational databases to support elastic, geographically distributed cloud environments.
NuoDB believes it has a solution to that. So too do others including GenieDB, Translattice and VMware. Meanwhile Google’s F1 and Spanner projects have legitimized the concept of the globally-distributed SQL database.
Either way, the era of the relational cloud database – rather than the relational database on the cloud – has begun.
January 14th, 2013 — Data management
Navigating our illustrated database landscape map. And more
And that’s the Data Day, today.
January 11th, 2013 — Data management
Anyone confused by our recently published database landscape map might be interested to know that 451 Research clients can now access an exclusive 451 Research guide to navigating the increasingly complex database landscape.
The guide steps through each of the main ‘lines’ and covers some of the issues we are seeing driving change across the the breadth of the map, as well as for individual lines. It is based on an updated January 2013 iteration of the map, which includes a number of revisions and additions based on feedback to the December 2012 version.
Note: the latest update to the map is available here.
Like any simplified illustration, the database map has its weaknesses – we certainly wouldn’t suggest that a company could use it to find an appropriate database for any given workload – but given the array of databases on the market, it is designed to help businesses identify a shortlist of potentially suitable choices based on the intersection of major functionality lines.
451 Research clients can access the guide here, while non-clients can use the same link to apply for trial access.
Subscribe via RSS