July 31st, 2013 — Data management
Next-Gen DB market sizing. Total Data Integration. And more.
And that’s the data day, today.
July 10th, 2013 — Data management
Oracle launches Database 12c. Predixion raises $20m. And more.
And that’s the data day, today.
April 26th, 2013 — Data management
Pivotal launches. SkySQL and Mony Program merge. And much, much more
April 15th, 2013 — Data management
I’ll be on a whistle-stop tour of California next week, including two presentations at the Percona Live MySQL Conference and Expo.
On day one at 1:20pm I’ll be presenting CAP Theorem: Two out of three ain’t right, in which I will be challenging the popular ‘two out of three’ explanation of CAP Theorem, examining the evidence from a variety of experts, including Dr Eric Brewer.
Then on day three at 9:00am I’m very honoured to be providing a keynote presentation, The State of the MySQL Ecosystem.
Here’s an overview of the presentation:
It is now over three years since Oracle acquired MySQL along with Sun Microsystems. Fears for the open source database’s survival appear to have been misplaced as Oracle has increased investment in MySQL development. At the same time, a thriving ecosystem of potential alternatives and complementary products has emerged to provide MySQL users with greater choice in terms of both functionality and support. As a result of that choice, we are seeing the increasing independence of the ecosystem of MySQL-related products and services from MySQL itself – both in terms of a commercial product, and also a development project. The continued maturity of vendors such as Percona and SkySQL, as well as the formation of the MariaDB Foundation, has the potential to accelerate that trend. The MySQL ecosystem is far from fragmenting, but 451 Research’s updated survey of database users indicates that the center of gravity has begun to shift towards an increased state of independence.
Beyond our own presentations of course there is a huge number of presentations of interest during the event from both users and vendors, and I’m looking forward to attending as well as presenting.
If you haven’t already registered you can do so now and get 15% off by using the code “SpeakMySQL” at checkout. Register here.
April 8th, 2013 — Data management
February 19th, 2013 — Data management
On February 28 at 1pm EST I’ll be taking part in a webinar, sponsored by ScaleBase, on strategies for scaling MySQL.
Scalability is one of the primary drivers we’ve seen for database users considering alternatives to traditional relational databases. That could mean adopting an entirely new database for new projects or – more likely for existing applications – looking at various strategies for improving the scalability of an existing database.
During the webinar I will be joined by Doron Levari and Paul Campaniello, both from ScaleBase, which enables applications to scale without disruption to the existing infrastructure. We’ll be discussing, amongst other things:
- Scaling-out your MySQL databases
- New high availability strategies
- Centrally managing a distributed MySQL environment
For further details, and to register, click here.
February 8th, 2013 — Data management
Teradata results. Funding for DataXu. The chemistry of data. And more.
And that’s the data day, today.
February 8th, 2013 — Data management
One of the most complicated aspects of putting together our database landscape map was dealing with the growing number of (particularly NoSQL) databases that refuse to be pigeon-holed in any of the primary databases categories.
I have begun to refer to these as “multi-model databases” in recognition of the fact that they are able to take on the characteristics of multiple databases. In truth though there are probably two different groups of products that could be considered “multi-model”:
True multi-model databases that have been designed specifically to serve multiple data models and use-cases
Examples include:
FoundationDB, which is being designed to support ACID and NoSQL, but more to the point in this instance, multiple layers including key-value, document, and object layers
Aerospike, which is planning to combine SQL, key value, and document and graph database technologies in a single database by bringing together its Citrusleaf NoSQL database with the acquired AlchemyDB NewSQL project
OrientDB, which is, at heart, a document database, but can also be used as a graph database; as an object database, making use of the Java persistence API; and as a hybrid database, taking advantage of multiple models to serve different application requirements
ArangoDB, which promises to deliver the benefits of key value and document and graph stores in a single database
Other products that could be considered true multi-model databases are:
Couchbase Server 2.0, which can be used as both a document store and a key value store, as well as a distributed cache
Riak, which is a key-value store, although it can be used as a document store since the value can be a JSON document
NuoDB, which will provide compatibility with other databases by taking on multiple ‘personalities’ – an Oracle personality via PL/SQL compatibility is in the development roadmap, as is a document store personality via JSON support.
General-purpose databases with multi-model options
What’s the difference between multi-model databases and existing general-purpose databases that have optional capabilities for serving multiple models? My book book it’s about being designed for purpose, but I’m sure that will be a debating point for the future. In the mean-time, examples include:
Oracle MySQL 5.6, which can support both SQL-based access and key-value access via the Memcached API.
Oracle MySQL Cluster 7.2, which similarly supports concurrent NoSQL and SQL access to the database.
IBM DB2 10, which extends DB2’s hybrid relational and XML engine to enable the storage and management of graph triples, as well as support for the SPARQL 1.0 query language.
Akiban Server, which has the ability to treat groups of tables as objects and access them as JSON documents via SQL.
PostgreSQL h-store, which can be used for storing key-value pairs within a PostgreSQL data field, thereby enabling schema-less queries against data stored in PostgreSQL
We are also aware of other NewSQL database that plan to adopt support for popular NoSQL data models, while IBM has also talked about plans to integrate key value store NoSQL access capabilities with DB2 and Informix database software.
Other products that could be considered multi-model options include:
Oracle Spatial and Graph, an option for Oracle Database 11g.
One of the drivers of NoSQL database adoption has been polyglot persistence – using multiple databases depending on the specific requirements of individual applications. Multi-model databases contradict this trend, to some extent, so it will be interesting to see whether they begin to gain traction.
While we see the wisdom of selecting the best database for the job, we also recognise that it could sometimes be a matter of choosing the best data model for the job, while relying on a single storage back-end.
February 6th, 2013 — Data management
Oracle launches MySQL 5.6. IBM expands PureData line. And more
And that’s the data day, today.
February 4th, 2013 — Data management
Fedora confirms MariaDB plans. IBM acquires Star Analytics. And more
And that’s the data day. today.
Subscribe via RSS