“Application designers need to start by thinking about what level of data integrity they need, rather than what they want, and then design their technology stack around that reality. Everyone would like a database that guarantees perfect availability, perfect consistency, instantaneous response times, and infinite throughput, but it´s not possible to create a product with [...]
4 Older Entries »
DataStax and VoltDB launch their version 3.0s. And more
For 451 Research clients: DataStax adds security and manageability to distributed NoSQL database bit.ly/Vb1IiT
— Matt Aslett (@maslett) January 18, 2013
For 451 clients: LogiXML serves up fresh cut of BI stack with an eye to more embedded analytics deals bit.ly/SppzsH By Krishna Roy
— Matt Aslett (@maslett) January 21, 2013[Read more]
451 Research’s 2013 Database survey is now live at http://bit.ly/451db13 investigating the current use of database technologies, including MySQL, NoSQL and NewSQL, as well as traditional relation and non-relational databases.
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.
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 …[Read more]
Two cons against NoSQL data stores read like this: 1. It’s very hard to move data out from one NoSQL to some other system, even other NoSQL. There is a very hard lock in when it comes to NoSQL. If you ever have to move to another database, you have basically to re-implement a lot [...]
“While I believe that one size fits most, claims that RDBMS can no longer keep up with modern workloads come in from all directions. When people talk about performance of databases on large systems, the root cause of their concerns is often the performance of the underlying B-tree index”– Martín Farach-Colton. Scaling MySQL and MariaDB [...]
“Legacy MySQL does not scale well on a single node, which forces granular sharding and explicit application code changes to make them sharding-aware and results in low utilization of severs”– Dr. John Busch, Schooner Information Technology A super-set of MySQL suitable for Big Data? On this subject, I have interviewed Dr. John Busch, Founder, Chairman, [...]
DOCOMO adopts, invests in Couchbase. Apache Cassandra reaches 1.0. And more.
# The Apache Software Foundation announced Apache Cassandra v1.0.
# Nuxeo announced the availability of Nuxeo Cloud.
# SGI formed a distribution relationship with Cloudera and …[Read more]
Red Hat revenue up 28% in Q2. Funding for NoSQL vendors. And more.
# Red Hat reported net income of $40m in the second quarter on revenue up 28% to $281.3m.[Read more]
Groklaw declares victory. Cloudera updates Hadoop distro. And more.
# Groklaw claimed victory, will stop publishing new articles on May 16.
# Cloudera released version 3 of its Hadoop distribution.
# VoltDB released version 1.3 of its open source distributed in-memory database.
# Black Duck grew sales by 51% in Q1.
# eXo and Convertigo …[Read more]
I’m not sure how many of this blog’s readers are likely to be aware of VoltDB. It is one of the systems that I think could be poised to dispel the notion that SQL (or the relational model) is somehow inherently unscalable. Here’s a blog post explaining how VoltDB does transaction ordering and replication.
- Why MySQL replication is better than mysqlbinlog for recovery
- What are your favorite MySQL replication filtering rules?
4 Older Entries »