[Update: 10/13/09: I’ve revised my thinking on the cloud as the term is loaded and doesn’t really mean what I’m describing. A friend from the San Diego Supercomputer Center said, “some greybeards are going back to the original metaphor: the grid” and suggested the term “shared digital libraries” which is good. But what I’m describing is more like a biological ecosystem, the FDLP ecosystem. jrj]
Last week’s GPO purl server crash should be disconcerting to both the documents community and the public at large (in fact, although the hardware’s been restored, resolution is ongoing as I write). I know GPO staff are just as worried about this and are doing everything they can to fix the purl server.
“The PURL Server is currently inaccessible. GPO is working with IT staff to restore service as soon as possible. We regret any inconvenience caused by the server problems. An updated listserv will be sent once service is restored.”
But in the meantime, there are 1250+ library catalogs and innumerable links to government documents that are not working. The crash of a critical piece of GPO’s infrastructure brings a couple of things to mind:
1) What worries me about this is that FDsys and it’s supposed upgrade in hardware/software/systems design is for all intents and purposes the same as GPOaccess. That is, FDsys is a monolith where the failure of one piece can cause the whole system to ground to a halt. As our readers know, we’ve been advocating for a long time for a distributed digital FDLP (a *true* “digital depository” system!). We’re heartened by what we see of FDsys so far, but we need to be building a system with built-in redundancies.
I envision a collaborative and distributed system of digital content, collaborative cataloging/metadata creation, as well as technical infrastructure. With this kind of system in place, a failed purl server will only cause a momentary blip in service as a backup purl server kicks on instead of a several week+ outage. How many system degradations (WAIS) and failures (purl server) until we shift our thinking from “[w:client-server]” (with libraries decidedly on the “client” side of the equation) to “[w:Peer-to-peer]” concepts and build systems with built-in redundancies that mirror what the FDLP has been for the last 150 years? How long before we build an FDLP cloud?