Search results

The purpose of this article is to provide an overview of current uses of cloud computing (CC) services in libraries, address a gap identified in integrating cloud storage in IaaS level, and show how to use EC2 tools for easy backup and resource monitoring.

The article begins a literature review of CC uses in libraries, organized at the SaaS, PaaS and IaaS levels. The author presents his experience of integrating cloud storage services S3 and GCS. In addition, he also shows how to use virtual machine EC2 tools for backup and monitoring resources.

The article describes a case study of integrating cloud storage using S3 and GCS. S3 can be integrated with any program whether the program runs on cloud or locally, while GCS is only good for applications running on GAE. The limitation of the current GCS approach makes it hard to use for a stand‐alone cloud storage. The author also discusses virtual machines using EC2 and its related tools for backup, increase storage, and monitoring service. These services make system administration easier as compared to the traditional approach.

The article presents current CC uses in libraries at the SaaS, PaaS, and IaaS levels. CC services are changing quickly. For example, Google has stated that its APIs are experimental. Readers should be aware of this.

The author shows his experience of integrating cloud storage services. Readers can understand the similarities and differences between S3 and GCS. In addition, readers can learn the advantages and concerns associated with implementing cloud computing. Readers are encouraged to consider questions such as content, skills, costs, and security.

There are many uses of CC services in libraries. However, gaps are identified: in IaaS cloud storage, a few libraries used Amazon S3 and Microsoft Azure, but none explored using Google Cloud Storage (GCS); none provided implementation details, difficulties, and comparisons of S3 and GCS; and a few articles have briefly discussed implementations on Amazon EC2, but have not provided specific details about upgrade and backup. This article addresses those gaps.

The purpose of this paper is to explore the evolving field of cloud computing and its usefulness for library technology departments. It seeks to consider what types of projects are good candidates for the cloud and which are not.

The authors spent a year trying out different projects using Amazon's Web Service. They discuss what went right and what went wrong. They brought up their own machine image and tested out web sites and applications in the cloud. They discuss the different types of cloud services, evaluating and choosing a provider and the types of projects which best fit into this architecture. Advantages and considerations are highlighted as well as an alternative to the public cloud.

There are some projects that are better suited to cloud computing than others. Flexibility and cost savings are the best reason for moving projects to the cloud. There are also good and valid reasons not to move some projects off into the cloud.

This is an on‐the‐ground look at running projects in the cloud that used to be done on back‐end servers. The bulk of the paper looks at infrastructure as a service. All of the work that has been done is in production and has been tested for over a year.