"Battle of the Clouds". Economist 392.8653 (17 Oct 2009): 16.
This article explores cloud computing within the frame of its technological history and future. It points out that cloud computing could easily follow the traditional path of new technological advances, that of big firms battling over who can make the most money off of it. However, cloud computing in some ways inherently supports the little guy. Since the cloud can act like a utility in that you pay for what you use, owning a bunch of servers is no longer a prerequisite to starting a computer business. It would seem like this would help create competition and prevent monopolies from forming, but the history of computing tends to show otherwise.
The article pinpoints "technological lock-in" as a sign that the battle of the clouds has begun. This term, which describes companies who develop standards and formats for their own systems that cannot communicate with any others, reminded me of Wheeler and Waggener's article about cloud computing for universities. Both articles discuss the need for an open cloud to maximize benefit. Since the cloud is a Web 2.0 technology that centers around sharing and networking, it seems ironic to me that companies are trying to reduce the amount of sharing that can be done. Based on Tim O'Reilly's theory, it seems like the more a company participates in web sharing, the more successful they should be. The article casts doubt on the claim that one company will end up dominating the cloud, but does not seem to refute the idea that the current major computing companies will eventually control the cloud. Given the short and transient nature of companies in the computer field thus far, it is impossible to predict what will happen in therms of computer company dominance. The article plays its predictions safely by only naming companies in the current struggle and keeping future descriptions vague.
The article touches on cloud search history and its potential effect on companies. Though information agencies are not specifically mentioned, this aspect of cloud computing may well be one of the biggest hurdles for libraries who want to use the cloud. Search history in the cloud can be stored forever, and since libraries (or other institutions) would not have direct control over it, it would be easy for the cloud company to view it without the library's knowledge or to use it for their own data-gathering. The article points out that making cloud systems reliable should currently be a top priority for companies that want to attract customers. I wholeheartedly agree, and would add trustworthy to that statement as well. I think librarians concerned about privacy and censorship would be at least as concerned about trust in the cloud as they are about cloud reliability.
Saturday, November 21, 2009
Friday, November 20, 2009
Resource Review #7 Above-Campus Services: Shaping the Promise of Cloud Computing for Higher Education
Wheeler, Brad and Waggener, Shelton. "Above-Campus Services: Shaping the Promise of Cloud Computing for Higher Education". EDUCAUSE Review, 44.6 (2009): 52-67.
This article focuses on how cloud computing can improve university services. I had not yet read an article about cloud computing from this perspective, and so learned quite a bit from it. The authors believe that cloud computing in a university setting can create completely new capabilities and opportunities. For it to work best and provide the maximum benefit to everyone, universities need to be active participants in the scholarly community. Wheeler and Waggener envision the cloud as becoming a "framework of open materials and platforms on which much of higher education worldwide can be constructed or enhanced." If universities use the cloud to collaborate, everyone will benefit from the shared resources and cost savings. They use the HathiTrust as an example, a book digitization project launched by the University of Michigan and Indiana University. They point out that it would not make much sense for every university to digitize the same books. By making these books available for others to see, either through public domain or with copyright regulations, all universities can benefit.
For me, an interesting aspect of the article is that it does not label the cloud as being either dangerous or essential. The tone is positive, and there are no warnings about either becoming too dependent on the cloud or not using it enough. Wheeler and Waggener focus on power of the universities to choose how they use the cloud. They list ways cloud technology can further university goals, but the results are largely dependent on how collaborative universities wish to be. I really like the emphasis they place on individual university choice. The way they discuss cloud computing in their article reminds me that it is in fact a tool that can be used in various ways to fit our needs. I think the topic of cloud computing often elicits strong reactions, and it is seen as the new technology that is taking over the world and there is nothing we can do about it. There are more options than just to swallow it whole or dig a hole to hide from it. Wheeler and Waggener do a great job of framing cloud computing in a way to show that there really are more than just these two options.
One of the main strengths of this article is that it explores cloud computing in the light of the university setting, not universities in the light of the cloud computing setting. Wheeler and Waggener describe the positive characteristics of academia and how cloud computing can best compliment those. Their article is a reminder that, for universities, there is already an adequate framework in place for incorporating new technology. I think this approach removes much of the fear and uncertainty that can surround cloud computing, and is a great guide for universities thinking about pursuing it.
This article focuses on how cloud computing can improve university services. I had not yet read an article about cloud computing from this perspective, and so learned quite a bit from it. The authors believe that cloud computing in a university setting can create completely new capabilities and opportunities. For it to work best and provide the maximum benefit to everyone, universities need to be active participants in the scholarly community. Wheeler and Waggener envision the cloud as becoming a "framework of open materials and platforms on which much of higher education worldwide can be constructed or enhanced." If universities use the cloud to collaborate, everyone will benefit from the shared resources and cost savings. They use the HathiTrust as an example, a book digitization project launched by the University of Michigan and Indiana University. They point out that it would not make much sense for every university to digitize the same books. By making these books available for others to see, either through public domain or with copyright regulations, all universities can benefit.
For me, an interesting aspect of the article is that it does not label the cloud as being either dangerous or essential. The tone is positive, and there are no warnings about either becoming too dependent on the cloud or not using it enough. Wheeler and Waggener focus on power of the universities to choose how they use the cloud. They list ways cloud technology can further university goals, but the results are largely dependent on how collaborative universities wish to be. I really like the emphasis they place on individual university choice. The way they discuss cloud computing in their article reminds me that it is in fact a tool that can be used in various ways to fit our needs. I think the topic of cloud computing often elicits strong reactions, and it is seen as the new technology that is taking over the world and there is nothing we can do about it. There are more options than just to swallow it whole or dig a hole to hide from it. Wheeler and Waggener do a great job of framing cloud computing in a way to show that there really are more than just these two options.
One of the main strengths of this article is that it explores cloud computing in the light of the university setting, not universities in the light of the cloud computing setting. Wheeler and Waggener describe the positive characteristics of academia and how cloud computing can best compliment those. Their article is a reminder that, for universities, there is already an adequate framework in place for incorporating new technology. I think this approach removes much of the fear and uncertainty that can surround cloud computing, and is a great guide for universities thinking about pursuing it.
Saturday, November 7, 2009
Resource Review #6 Libraries in the Cloud: Making a Case for Google and Amazon
Buck, S. Libraries in the Cloud: Making a Case for Google and Amazon. Computers in Libraries v. 29 no. 8 (September 2009) p. 6-10
The author of this article, Stephanie Buck, defines herself as a MLS student at Simmons College, a fact I am impressed with considering her accomplishment of being published in the Computers in Libraries journal. The article covered the same bases as most introduction-to-cloud-computing articles, but its particular strength was describing the cost-effectiveness of the cloud model for libraries. The Google Apps suite costs $50 dollars a year, and operates comparably to the Microsoft Office Suite, which costs $500 dollars a year. The switch would equal huge savings for libraries. Another application, Amazon's S3, a cloud data storage system, charges are associated with individual requests for storage and transfer, so libraries only pay for what they use. Buck suggests using money saved on software for other places within the IT budget.
However, Buck is quick to point out that the cloud is not a perfect storage alternative in terms of cost. Traditional internal storage systems aim to reduce cost to the customer over a period of time by transferring older and less-accessed data to less expensive media. Current cloud computing companies charge exactly the same no matter how long the data has been stored. Consequently, cloud storage could potentially cost more long-term. Personally, I think that since cloud computing has not been around very long, it is impossible to predict how favorable it will be to store data long-term on the cloud. I am sure as cloud storage techniques become more fine-tuned and culturally popular that companies will adjust their rates to be competitive.
There is also the cost issue of migrating internally stored data to cloud applications, and the future potential for having to migrate data from one cloud application to another. Just because data is stored on the cloud does not mean its storage techniques will remain eternally viable. One librarian who is considering Amazon's S3 for his library commented that for him there is really no difference between having to migrate because of hardware obsolescence or service obsolescence, and that the faster retrieval times for patron requests and the clearing of local server space make the cloud option appealing. I agree with this reasoning. Considering how much sense cloud computing makes for libraries from an economic and service prospective, as well as its increasing popularity with the general public, I think it is the necessary technological future for libraries.
The author of this article, Stephanie Buck, defines herself as a MLS student at Simmons College, a fact I am impressed with considering her accomplishment of being published in the Computers in Libraries journal. The article covered the same bases as most introduction-to-cloud-computing articles, but its particular strength was describing the cost-effectiveness of the cloud model for libraries. The Google Apps suite costs $50 dollars a year, and operates comparably to the Microsoft Office Suite, which costs $500 dollars a year. The switch would equal huge savings for libraries. Another application, Amazon's S3, a cloud data storage system, charges are associated with individual requests for storage and transfer, so libraries only pay for what they use. Buck suggests using money saved on software for other places within the IT budget.
However, Buck is quick to point out that the cloud is not a perfect storage alternative in terms of cost. Traditional internal storage systems aim to reduce cost to the customer over a period of time by transferring older and less-accessed data to less expensive media. Current cloud computing companies charge exactly the same no matter how long the data has been stored. Consequently, cloud storage could potentially cost more long-term. Personally, I think that since cloud computing has not been around very long, it is impossible to predict how favorable it will be to store data long-term on the cloud. I am sure as cloud storage techniques become more fine-tuned and culturally popular that companies will adjust their rates to be competitive.
There is also the cost issue of migrating internally stored data to cloud applications, and the future potential for having to migrate data from one cloud application to another. Just because data is stored on the cloud does not mean its storage techniques will remain eternally viable. One librarian who is considering Amazon's S3 for his library commented that for him there is really no difference between having to migrate because of hardware obsolescence or service obsolescence, and that the faster retrieval times for patron requests and the clearing of local server space make the cloud option appealing. I agree with this reasoning. Considering how much sense cloud computing makes for libraries from an economic and service prospective, as well as its increasing popularity with the general public, I think it is the necessary technological future for libraries.
Subscribe to:
Comments (Atom)