today's leftovers:
Submitted by srlinuxx on Thu, 03/11/2010 - 00:49
- A quick look at some new features in Banshee 1.5.5
- A Year of Quake Live
- Google's Slow March Toward World Domination
- Multi Tail – Multi Tail!
- Turn your old computer into a music server with VortexBox Linux
- What CPAN Doesn't Do
- PCLinuxOS 2010 Beta 1
- All Hail Our Benevolent Corporate Overlords
- The MicroShills Are At It Again
- The Linux Foundation Store: Linux gets silly
- Updating the Mozilla Public License
- Linux struggles to make a dent in desktop
- IMDbPY projects IMDb.com data onto your screen
- Microsoft's Internet Driving Licence: stupid, unworkable and unenforceable
- Mozilla refreshes its open-source backbone
- And the winner of the Novell sweepstakes is...Microsoft?
- Peering at Paldo 1.21
- City of Athens using Drupal
- A Bright Future for Drizzle
- Dominions 3: The Awakening v3.24 Released
- Meet the GIMP: Episode 135 - Darktable
Drizzle vs MySql nodes with unionfs or aufs ? Kernel dependent
Kernel v2.6.x started the difficult task of handling distributed database. Cron jobs got complicated and still not working. So, database such as MySql is best working with single server indexed for IP addresses. Drizzle being originally sponsored by Sun, did not get anywhere with Linux unionfs and aufs. Some where on the way to the forum, unionfs and aufs got side tracked to support Linux kernel and apps update at various repository(synaptic). Whereas distributed databases need cron jobs for data update in drams(terabyte appliance). Which needs crossbar packet switching depending on the data input location, and the rest of the distributed data storage and delivery points.
So, its still indexed servers winning the job of handling distributed database. SQL keyword search engine will get all the database regardless of locations. Cron jobs are not efficient as a basic principle of storing database in many locations. However, sooner or later cron jobs can be a savior of backup requirement. Multiple copies of database can avoid denial of service, and maintain data that will never be corrupted.
Unionfs and aufs had to have specific database hooks to do a thorough cron job with checksum, date stamped by miniature atomic clocks.