The Almanac: Storage
687781
â¢ Optware Corp. in Japan (www.optware.co.jp/english) has come out with a prototype of what it calls the world&#39;s first holographic recording disc for reliable recording and playback of digital movies.
626630
Enhanced midrange storage array, network hardware released.
385505
When Amazon introduced S3 a couple of years ago I knew I would useit and I was sure a lot of other developers would. I saw it as a solution to a problem we all have -- storage that scales up when needed, and scales down when not. Otherwise we all have to buy as much bandwidth as we need in peak periods. With S3, you pay for what you use. It makes storage for Internet services more rational. Later they did the same for processors and queuing. And a couple of days ago they announced a lightweight scalable database, using the same on-demand philosophy and simple architecture and API. It's going to be a huge hit and forever change the way apps are developed for the Internet. I was explaining the significance of this to Scoble on the phone this morning. It's worth repeating here. When I developed Frontier in the late 80s and early 90s my target platform was a modern desktop computer, a few megabytes of RAM, a half-gig of disk, a few megahertz CPU. A system capable of running Quark XPress, Hypercard or Filemaker. It would be used to develop apps that would drive desktop publishing. Later, it was used to generate static websites, then a demonstration of democracy (a multi-author ultra-simple CMS), then news sites, which became weblogs, then blogs, and editthispage.com, Manila, weblogs.com, and that's when scaling became an issue. (Later we side-stepped the scaling issue by moving most of the processing to the desktop with Radio 8.) As we approached then cracked ease of use in web authoring, scaling became an issue, then the issue. A Manila server would work fine for a few thousand sites, but after that it would bog down because the architecture couldn't escape the confines of a single machine it was designed for in the 80s. (Before you say it's obsolete, there still are a lot of apps for single machines. Perl, Python, JavaScript and Java share the same design philosophy.) Same with weblogs.com. It worked great when there was a few thousand blogs. Once we hit 50K or so, we had to come up with a new design. Eventually we were tracking a couple million, and Frontier was hopelessy outclassed by the size of the problem. If only Amazon's database had been there, both Manila and weblogs.com could have been redesigned to keep up. It would have been a huge programming task, but it would have made it economically possible.  Today, when a company raises VC, it's probably because their app has achieved a certain amount of success and to get to the next level of users they need to spend serious money on infrastruture. There's a serious economic and human wall here. You need to buy hardware and find the people who know how to make a database scale. The latter is the hard problem, the people are scarce and the big companies are bidding up the price for their time. Now Amazon is willing to sell you that, to turn this scarce thing into a commodity, at what likely is a very reasonable price. (Haven't had time to analyze this yet, but the other services are.) Key point, the wall is gone, replaced with a ramp. If you coded your database in Amazon to begin with you will never see the wall. As you need more capacity you have to do nothing, other than pay your bill.  Further, the design of Amazon's database is remarkably like the internal data structures of modern programming languages. Very much like a hash or a dictionary (what Perl and Python call these structures) or Frontier's tables, but unlike them, you can have multiple values with the same name. In this way it's like XML. I imagine all languages have had to accomodate this feature of XML (we did in Frontier), so they should all map pretty well on Amazon's structure. This was gutsy, and I think smart.  They're going down a road we went down with XML-RPC and then SOAP. There may be some bumps along the way but there are no dead-ends, no deal-stoppers. All major environments can be adapted to work with this data structure, unless I'm missing something (standard disclaimers apply). Their move makes many things possible. As I said earlier, if it existed when we had to scale weblogs.com, we would certainly have used it. One could build an open identity system on it, probably in an afternoon, it would be perfect for that. A Twitter-like messaging system, again, would be easy. It's amazing that Microsoft and Google are sitting by and letting Amazon take all this ground in developer-land without even a hint of a response. It seems likely they have something in the works. Let's hope there's some compatibility.
449214
News and survey results from Computerworld's twice-annual storage conference.
480867
New drive crams enormous storage capacity into standard 3.5-inch format, but it's not ready for delivery just yet.
766872
Data Deposit Box service makes off-site data storage easy, inexpensive.
74566
Personal computers have rapidly turned into storage vaults for digital music, photos and videos. Now, computer-industry companies are rolling out new ways to let that content roam through the house.
592564
A new study that estimates how much digital information is zipping around (hint: a lot) finds that for the first time, there's not enough storage space to hold it all. Good thing we delete some stuff.
420884
NEW YORK - Now that digital music players have evolved beyond the ability to store 20 gigabytes worth of music, storage capacity memory is no longer the only factor to consider before buying.
370325
roundup Plus: SanDisk ups capacity on flash memory cards...Google tests Froogle in U.K....Senate postpones vote on file-swapping bill...HP may expand Puerto Rican research.
620607
There are many advantages - and hazards - involved in backing up today's  small office data. Here's some help.
705381
Continuing the thread on commoditization of scalable server software, the third installment. Yesterday, Matt Tucker from the OpenFire community, said: "I'm not sure that S3 magically kills off the scaling priests. It certainly makes it easy to turn on more storage resources, but writing an application to scale efficiently across multiple virtual machines is no easy task." To which I responded... It won't make scaling obsolete, but what it does do is commodify it. Right now I can't buy a Jabber server that scales without also hiring someone who will scale it for me. But in a few years I should be able to buy a Jabber server that, when it needs more CPUs, just asks for them all transparently to the user, the same way my word processor asks the OS for more memory today. I remember word processors that didn't do memory management, you got a 64K buffer and that's it. One document. When you filled it up, you started another. Technology will go forward and scaling won't be a black art, it'll be something built into the software you license.
287000
A sleek home-media PC looks creamy delicious; a carry bag becomes a chair storing laptop; and more. By Brian Lam from Wired magazine.
323917
Storage Expo Iomega punts a hard disk autoloader
447801
New TagmaStore plays well with rivals' arrays to keep watch over 32 petabytes of data.
700075
By BRIAN BERGSTEIN BOSTON - A new study that estimates how much digital information is zipping around (hint: a lot) finds that for the first time, there's not enough storage space to hold it all. Good thing we delete some stuff.
94900
DS8000, DS4000, DS3000, TS2240, TS7520 please come to the red courtesy phone IBM is releasing details on a lot of storage stuff today. We mean a lot.â¦