drizzle: All content tagged as drizzle in NoSQL databases and polyglot persistence
Wednesday, 16 March 2011
MySQL Fork Drizzle Released
Drizzle aims to be different from MySQL, stripping out “unnecessary” features loved by enterprise and OEMs in the name of greater speed and simplicity and for reduced management overhead.
Drizzle has no stored procedures, triggers, or views […]
Aiming to provide a database for the cloud with support for massive concurrency optimized for increased performance, Drizzle team started by removing “non-essential” code and features. Michael Stonebraker’s VoltDB is focusing on a different set of optimizations for achieving performance — removing logging, locking, latching, buffer management[1].
Anyway, it is not about who’s approach is better, but which scenarios are covered by using a simplified MySQL compatible database or by an in-memory with predefined queries database.
-
The “NoSQL” Discussion has Nothing to Do With SQL:
If one eliminates any one of the above overhead components, one speeds up a DBMS by 25%. Eliminate three and your speedup is limited by a factor of two. You must get rid of all four to run a lot faster.
Original title and link: MySQL Fork Drizzle Released (NoSQL databases © myNoSQL)
via: http://www.channelregister.co.uk/2011/03/16/drizzle_released/
Wednesday, 23 December 2009
Drizzle Replication: Opening the Doors to Hybrid Solutions
I don’t know how many have heard of or used Drizzle [1], the MySQL engine optimized for cloud and net applications, but there seems to be some activity (from Marcus Eriksson) around creating Drizzle replication to different NoSQL stores: Project Voldemort and memcached [2] or Cassandra [3].
Leaving aside the technical details — which are definitely interesting [4], the solution using the Erlang AMQP [5] implementation RabbitMQ [6] — I think this replication layer could represent a good basis for SQL-NoSQL hybrid solutions, which is a direction we’ve mentioned before: Introducing the Oracle-SimpleDB Hybrid
It would be interesting to hear other stories from those that are investigating the NoSQL hybrid solutions.
And while we are at MySQL engines, I thought I should also mention this question from Ilya Grigorik (@igrigorik):
anyone try or using TokuDB [7]? drop in MySQL engine using fractral trees, claims 10-50x over InnoDB, etc.
