Cloud Services
11 likes4,499 views
The document discusses cloud services and why developers should build them. It defines cloud services using examples like Amazon S3 for file storage and New Relic for performance monitoring. These services take over infrastructure headaches like scaling by running software as hosted, managed services where the provider handles operations and maintenance in exchange for usage-based fees. The document argues the cloud services market is emerging and offers exciting opportunities to develop new offerings.
Cloud Services
- 1. Cloud Services What they are, and why you should build one Adam Wiggins Gluecon 2010
- 5. Defining “cloud service” by example
- 6. Amazon S3
- 7. Amazon S3 binary asset cloud service
- 8. Binary assets aren’t hard
- 9. Binary assets aren’t hard ...until you need to scale
- 10. Outsource the headache of binary assets to S3
- 11. New Relic
- 12. New Relic performance metrics cloud service
- 13. Storing metrics and rendering graphs isn’t hard
- 14. Storing metrics and rendering graphs isn’t hard ...until you need to scale
- 15. Outsource the headache of performance metrics to New Relic
- 17. Send/recieve email from your app
- 18. Email isn’t hard
- 19. Email isn’t hard ...until you need to scale
- 20. Outsource the headache of email to...
- 21. ‣Authsmtp
- 24. Can we take it further?
- 25. Database
- 26. Running a database isn’t hard
- 27. Running a database isn’t hard ...until you need to scale
- 28. Outsource the headache of running a database
- 29. ‣MongoHQ
- 34. The pattern
- 36. Run as a hosted, managed service
- 37. Ops, scaling, maintenance handled by the cloud service provider
- 38. Customer pays provider proportional to usage
- 39. Why should you build a cloud service?
- 40. An emerging market full of exciting opportunities
- 41. Now is the perfect time to build a cloud service