This document discusses libraries moving services to the cloud. It begins by defining cloud computing and the different types of cloud models including infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). Examples are given of how libraries currently use each cloud model. Considerations for libraries transitioning to the cloud include budget, personnel needs, bandwidth requirements, and service level agreements. The presentation raises questions about reliability, control, and the risks of vendor lock-in.

1. LIBRARIES IN THE CLOUD
Krista Godfrey
kgodfrey@mun.ca

2. http://bit.ly/HbPoX3
WHAT IS THE CLOUD?

3. http://bit.ly/Yj7FES
WHAT DOES IT MEAN?
Move from procuring and deploying to management &
provision of resources

4. WHY THE FUSS?

5. TO THE
CLOUD!
http://bit.ly/HbReHn

6. DO YOU USE
THE CLOUD?
A. Yes, all the time
B. Yes, but not for sensitive
info
C. No, I don’t trust it
D. No, I don’t have a good
enough connection
E. Not sure if I use it http://bit.ly/Yj7pWs

7. http://bit.ly/VRUIr6
FEATURES
• On-demand self service • Resource Pooling •Measured service
• Broad network access • Rapid Elasticity

8. http://bit.ly/VvAi1d
CLOUD TYPES
•Public •Community •Private •Hybrid

9. http://bit.ly/Y22flC
CLOUD VARIATIONS
• IaaS •PaaS • SaaS
Infrastructure as a Service Platform as a Service Software as a Service

10. http://bit.ly/HbPPR7
IAAS
• Provides access to hardware, removing cost of owning/purchasing it
• Still requires expertise
• Ex. Amazon web services

11. http://bit.ly/HbOHVV
PAAS
• Provides tools and space for development
• Build, test, deploy web-based apps
• Ex. Facebook Developers, Google App Engine, Windows Azure

12. http://bit.ly/HbPBcP
SAAS
• Provides access to software
• Most common and requires the least amount of expertise and customization
• Ex. Gmail, Flickr, Twitter

13. WHY GO TO
THE CLOUD?
•Collaboration •Flexibility
•Security •Scalability
•Reliability •Cost
•Access •Green
http://bit.ly/HbQ26S

14. WHAT TO
KEEP IN MIND
•Privacy •Reliability/
•Legal Issues Service
•Data Disruptions
Ownership •Control
http://bit.ly/HbQ26S

15. http://bit.ly/Vvz71U
LIBRARIES & THE CLOUD

16. IS YOUR
LIBRARY IN
THE CLOUD?
A. Yes
B. No
C. Not sure
http://bit.ly/VRVVPf

17. LIBRARIES &
IAAS
Amazon Web Services
• Elastic Compute Cloud
(EC2)
• Simple Storage Service (S3)
http://bit.ly/Yj7KZa

18. LIBRARIES &
PAAS
•Google App Engine
• Windows Azure
•Heroku
•ILS
http://bit.ly/GRJ3Np

19. LIBRARIES &
SAAS
• LibGuides • Document
• Jing Storage
• Slideshare • ILS
• PollAnywhere • Discover Layers
• Flickr • OpenURL
• YouTube Resolvers
• Twitter • OPACs
• Stackmap • Ejournal Portals
• IM • Citation
• Websites Managers http://bit.ly/VRVJiI

20. http://bit.ly/VaoxC0
CONSIDERATIONS
•Support/Reliability •Vendor Side Updates •Control/Security

21. http://bit.ly/VRWj02
BUDGET

22. http://bit.ly/VRWpEU
PERSONNEL

23. http://bit.ly/VRWsR3
BANDWIDTH

24. http://bit.ly/yVrNsG
SERVICE LEVEL AGREEMENTS

25. What happens if the company is sold/folds?
When is support offered?
What are your performance benchmarks?
Maintenance schedules
What is the guaranteed response time?
What support is offered?
What is the guaranteed uptime?
What happens if there is a breach?

26. http://bit.ly/yVrNsG
LOCK IN

27. http://bit.ly/VRWWGO
WHAT’S AHEAD?

28. http://bit.ly/VRWWGO
QUESTIONS?
e: kgodfrey@mun.ca
twitter: @weelibrarian