Planning Ahead for Open Source Storage Scaling

Posted in Tue, 24 Oct 2006 16:56:00 GMT

Recently eWeek ran an article on eHarmony's storage scaling solution choice which discussed how they chose to go with proprietary solutions from 3PAR and ONStor. I was hoping to learn something interesting about their deployment architecture but the most interesting things I learned was that eHarmony has 8+ million users, 9+ million photos and their proprietary solution vendor choice. Some interesting quotes from Mark Douglas, eHarmony's VP of Technology:

Read more...
del.icio.us:Planning Ahead for Open Source Storage Scaling digg:Planning Ahead for Open Source Storage Scaling reddit:Planning Ahead for Open Source Storage Scaling spurl:Planning Ahead for Open Source Storage Scaling wists:Planning Ahead for Open Source Storage Scaling simpy:Planning Ahead for Open Source Storage Scaling newsvine:Planning Ahead for Open Source Storage Scaling blinklist:Planning Ahead for Open Source Storage Scaling furl:Planning Ahead for Open Source Storage Scaling fark:Planning Ahead for Open Source Storage Scaling blogmarks:Planning Ahead for Open Source Storage Scaling Y!:Planning Ahead for Open Source Storage Scaling smarking:Planning Ahead for Open Source Storage Scaling magnolia:Planning Ahead for Open Source Storage Scaling segnalo:Planning Ahead for Open Source Storage Scaling

no comments

apple icon

iPod, iTunes and DRM

Posted in Thu, 19 Oct 2006 04:03:00 GMT

I've been a happy iPod user for some time now, however I've only ever used my single iPod with a single iTunes install. I recently reinstalled my OS after wiping the hard drive for a clean start. To my surprise a fresh install of iTunes with the same iPod serial number would not import songs from my iPod into the iTunes library. iTunes had the gall to ask me if I wanted it to erase all the music on my iPod and replace it with the (empty) contents in its library. Essentially my iPod was orphaned. I've never thought about Apple DRM issues before but I'm no longer as excited about the iPod and iTunes as I was before.

Read more...
del.icio.us:iPod, iTunes and DRM digg:iPod, iTunes and DRM reddit:iPod, iTunes and DRM spurl:iPod, iTunes and DRM wists:iPod, iTunes and DRM simpy:iPod, iTunes and DRM newsvine:iPod, iTunes and DRM blinklist:iPod, iTunes and DRM furl:iPod, iTunes and DRM fark:iPod, iTunes and DRM blogmarks:iPod, iTunes and DRM Y!:iPod, iTunes and DRM smarking:iPod, iTunes and DRM magnolia:iPod, iTunes and DRM segnalo:iPod, iTunes and DRM

6 comments

mysql icon

MySQL Deployment Presentations

Posted in , Fri, 06 Oct 2006 03:07:00 GMT

I just ran across the MySQL Web 2.0 page which lists a number of their users including the following:

MySQL Web2.0

The most interesting thing from that page, however, is links to various presentations given by those sites on how they architected their sites to scale with MySQL, some of them scaling up to hundreds of MySQL servers.

Read more...
del.icio.us:MySQL Deployment Presentations digg:MySQL Deployment Presentations reddit:MySQL Deployment Presentations spurl:MySQL Deployment Presentations wists:MySQL Deployment Presentations simpy:MySQL Deployment Presentations newsvine:MySQL Deployment Presentations blinklist:MySQL Deployment Presentations furl:MySQL Deployment Presentations fark:MySQL Deployment Presentations blogmarks:MySQL Deployment Presentations Y!:MySQL Deployment Presentations smarking:MySQL Deployment Presentations magnolia:MySQL Deployment Presentations segnalo:MySQL Deployment Presentations

2 comments

perl iconmysql iconunicode icon

Perl, MySQL and UTF-8

Posted in , , , Mon, 02 Oct 2006 15:35:00 GMT

One of the mysteries of Perl to me is that why, as of yet, is there no UTF-8 support in DBD::mysql although this issue has been discussed on the msql-mysql-modules list since at least 2003 (using the MARC archives). This is also given that MySQL does have UTF-8 support itself.

Read more...
del.icio.us:Perl, MySQL and UTF-8 digg:Perl, MySQL and UTF-8 reddit:Perl, MySQL and UTF-8 spurl:Perl, MySQL and UTF-8 wists:Perl, MySQL and UTF-8 simpy:Perl, MySQL and UTF-8 newsvine:Perl, MySQL and UTF-8 blinklist:Perl, MySQL and UTF-8 furl:Perl, MySQL and UTF-8 fark:Perl, MySQL and UTF-8 blogmarks:Perl, MySQL and UTF-8 Y!:Perl, MySQL and UTF-8 smarking:Perl, MySQL and UTF-8 magnolia:Perl, MySQL and UTF-8 segnalo:Perl, MySQL and UTF-8

8 comments

perl iconmysql iconxapian icon

Encoding Hashed UIDs: Base64 vs. Hex vs. Base32

Posted in , , Mon, 02 Oct 2006 08:08:00 GMT

I recently looked at using various encodings for hashed UIDs, e.g. UIDs generated by a crytographic hash algorithm such as SHA-1 or MD5. These are often useful when the UID does not need to have human meaning but should exhibit some uniformity, such as character set and length. I considered Base64 and hexadecimal first because they are commonly used by crypto libraries and then decided on Base64 and Base32 where appropriate. Base36 is actually the most compact case insensitive encoding (using Arabic numbers and Roman letters) but is not an option for me at the moment because there's no Perl module for it that will take arbitrary text and binary input at the moment. Math::Base36 exists but only handles numbers.

Read more...
del.icio.us:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 digg:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 reddit:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 spurl:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 wists:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 simpy:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 newsvine:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 blinklist:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 furl:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 fark:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 blogmarks:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 Y!:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 smarking:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 magnolia:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32 segnalo:Encoding Hashed UIDs: Base64 vs. Hex vs. Base32

no comments