This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes. This lecture will briefly introduce MySQL partitioning, and then show how to create and use the Spider engine, with some practical …

This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes. This lecture will briefly introduce MySQL partitioning, and then show how to create and use the Spider engine, with some practical …

This Thursday (October 15th, 13:00 UTC), Giuseppe Maxia will present the Spider Storage Engine. Here's from the abstract: Everybody needs sharding. Which is not easy to maintain. Being tied to the application layer, sharding is hard to export and to interact with. The Spider storage engine, a plugin for MySQL 5.1 and later, solves the problem in a transparent way. It is an extension of partitioning. Using this engine, the user can deal transparently with multiple backends in the server layer. This means that the data is accessible from any application without code changes. This lecture will briefly introduce MySQL partitioning, and then show how to create and use the Spider engine, with some practical …

The linux.conf.au organisers have given all miniconfs an additional few weeks to spruik for more proposal submissions, huzzah!

So if you didn’t submit a proposal because you weren’t sure whether you’d be able to attend LCA2010, you now have until October 23 to convince your boss to send you and get your proposal in.

Save the date - October 14th, 3pm Paris & Berlin, 2pm London, 4pm Jerusalem  -  for this free live webinar where you'll have a chance to ask questions to our experts.

This webinar focuses on how ZFS, SSDs and the Open Storage line of products from Sun are changing the rules in the database storage industry. You will learn how to increase data security, scalability, and reduce the price/performance ratio with these technologies. This webinar includes ZFS best practises for databases backup and performance.

To register, click here.

1. NASA Nebula Services/Platform Stack -- The NEBULA platform offers a turnkey Software-as-a-Service experience that can rapidly address the requirements of a large number of projects. However, each component of the NEBULA platform is also available individually; thus, NEBULA can also serve in Platform-as-a-Service or Infrastructure-as-a-Service capacities. Bundles RabbitMQ, Eucalyptus, LUSTRE storage, Fabric deployment, Varnish front-end, MySQL and more. (via Jim Stogdill)
2. …

Sun recently rolled out a new Business Intelligence (BI) solution that uses Open Storage at its core. There are several things that are different about this solution that make it stand out from the crowd.

1) It is based on Open Source software.

This solution uses the commercial versions of open source software from Pentaho and Infobright to provide the BI and Datawarehouse (DW) functions respectively and both use the MySQL database. Also, this solution uses Sun's Open Storage products as the core storage component which are built using Open Source software and industry standard components. Combine those with an Open Source operating system like Solaris or Linux and you have a complete BI solution built on an Open Source software stack.

2) The price is right. …

Sun recently rolled out a new Business Intelligence (BI) solution that uses Open Storage at its core. There are several things that are different about this solution that make it stand out from the crowd.

1) It is based on Open Source software.

This solution uses the commercial versions of open source software from Pentaho and Infobright to provide the BI and Datawarehouse (DW) functions respectively and both use the MySQL database. Also, this solution uses Sun's Open Storage products as the core storage component which are built using Open Source software and industry standard components. Combine those with an Open Source operating system like Solaris or Linux and you have a complete BI solution built on an Open Source software stack.

2) The price is right. …

Sun recently rolled out a new Business Intelligence (BI) solution that uses Open Storage at its core. There are several things that are different about this solution that make it stand out from the crowd.

1) It is based on Open Source software.

This solution uses the commercial versions of open source software from Pentaho and Infobright to provide the BI and Datawarehouse (DW) functions respectively and both use the MySQL database. Also, this solution uses Sun's Open Storage products as the core storage component which are built using Open Source software and industry standard components. Combine those with an Open Source operating system like Solaris or Linux and you have a complete BI solution built on an Open Source software stack.

2) The price is right. …

Yesterday I merged the BlitzDB tree with Drizzle‘s trunk for the first time in a long time (yeah…) and discovered some interesting changes made to the storage subsystem while I was away.

Previously all functions that caused an action to the storage engine was a member of the handler class but various things like table creation and transaction related functions have now moved to the StorageEngine class. These changes are somewhat drastic but makes good sense for Drizzle to grow further since it makes the subsystem easier to understand and frees Drizzle from the interface design that was strongly affected by MyISAM. For those that are interested, the StorageEngine class is located in “drizzled/plugin/storage_engine.h”.

For me it was pretty easy to update BlitzDB to work with the new …