Cloud computing and RePEc

Hosting RePEc services has been both a technical and an organizational challenge. Historically, the first hosting of what was to become RePEc goes back to late 1992. Manchester Computing Center, as it was known then, agreed to create WAIS indexed Gopher for the BibEc and WoPEc projects created by Thomas Krichel. The site was converted to the web in 1993. Manchester Computing Center were a national center for academic computing, providing services the UK academic community. They were fortunately forward-looking in their outlook when they started to with NetEc. It was broadly within their remit as Thomas Krichel worked in UK academia at the time. They continued to sponsor RePEc-related sites until the end of the decade. But they were not the only one. Washington University of St. Louis, where EconWPA was living, contributed a NetEc mirror, and so did Hitotsubashi University where Satoshi Yasuda kept as server in his documentation centre for Japanese economic statistics. So generally, it was for sponsoring institutions, where a RePEc volunteer lived to take up the hosting. If they agreed, there were usually stringent conditions. Machines are locked in a facility closed after hours, there are rules on firewalls. Or when the machine was based in somebody’s office, a cleaner could unplug a cable, electricity cuts could cause damage to the motherboard, failing air conditioning would damage disks. The list may look comical now, but at the time each incident was a disaster. There was not much of an alternative. Commercial solutions were too expensive to be paid for by an individual, and project funding would come to an end.

Things are looking better now. Cloud computing has become much cheaper. In 2006, the RePEc OAI gateway, sponsored by the Central Library of Economics (ZBW) in Germany was the first sponsored RePEc service. The CollEc service has become the second sponsored RePEc service. The server runs at a hosting company. The server is a dedicated machine, with 8 CPUs. They are running 100% constantly as the calculations for CollEc are very heavy, at this time. One single sponsor covers a 50 euros a month fee for the machine. In November 2012 the ZBW sponsorship moved to a similar machine. In December 2012, the NEP service followed. It uses a similar machine. The NEP team had several offers of sponsorship and chose the one by Victoria University of Wellington, mainly because they were the first to offer. We think the CitEc service will follow suit, but we still have to find a sponsor. We also could move the main RePEc site to a similar machine. While a single site may not require the use of a powerful computer we still need backup. Case in point, in 2008 staff at the hosting company discovered that the server sponsored by ZBW did not have a stick on it. They proceeded to dismantle the machine. No data was recoverable. Fortunately Thomas Krichel kept a backup.

We expect that RePEc will be using more sponsored hosting. It is a very good thing. RePEc volunteers have spent countless hours on broken disks, falling power supply systems, loose network cable than you can shake a stick at. Using sponsored hosting can leave more time to improve service.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: