Ruby in the Clouds
0 likes460 views
This document outlines an agenda for a conference session on Ruby in the clouds. It discusses cloud computing models like IaaS, PaaS, SaaS and BaaS. It notes that dedicated servers are becoming obsolete and cloud providers give developers choices and tools for app-centric development, scaling, and building blocks. Popular cloud platforms that support Ruby are mentioned like Heroku, Engine Yard, Google App Engine, Microsoft Azure and more. The document concludes by thanking attendees and providing a contact.
Ruby in the Clouds
- 1. Ruby in the Clouds RubyCamp Lyon 2010
- 2. Agenda What's Cloud Computing Vendors Demo
- 3. Ruby in the Clouds What's Cloud Computing
- 4. Cloud Computing 1/3 IaaS, PaaS, SaaS, BaaS Dedicated servers are dead (to me) You can't compete Choices remain YOURS
- 5. Cloud Computing 2/3 App-centric development (at last) Building blocks are yours Scaling is knowing your requirements
- 6. Cloud Computing 3/3 To wrap it up You already use (part of) it You should use it even more SWOT analysis not even needed Not too late to be part of it
- 7. Ruby in the Cloud Vendors
- 8. Vendors 1/2 You heard about them: AWS-based: Heroku Engine Yard Google App Engine Microsoft Azure ... And they all support Ruby...
- 9. Vendors 2/2 Fully customizable stack OS Interpreters Appication servers (we <3 Rack) / DB Frameworks Cache / Background processing
- 10. Ruby in the Clouds Demo Q&A
- 11. Thanks ! @CesarioGW http://www.dev-fr.com
Editor's Notes
- #5: From infrastructure to the whole business, everything is now avaiable as a service. 1. Virtualization won the game. Costly to maintain a server and hire qualified HR. 2. Small to medium ISV can't compete (expertise, time, investment). 3. No one else will make the choices for you. Cloud omputing won't prevent you from screwing up your projects.
- #6: The focus is given on what's essential: the application, not on &quot;how to host and monitor it&quot;. 1. The big picture is own by you, you know the blocks (db, app server, front end). 2. Scaling won't be guessed by the system, you have to configure the system so that you can monitor your app (Exceptional, Hoptoad, Errnot, ...)
- #7: 1... without knowing it. Saas is new name for a very old and common thing actually... 2. So easy to set up that you will use it, nobody likes to setup servers (even using Chef and vagrant). 3. Give it a shot, it's risk free. You're the customer and can opt out if you prefer to spend time configuring your machines. 4. It's still growing and searching for new ideas. You can eat a part of the cake by building an awesome app and be partner with EY or Heroku.
- #9: Choose one of the best player: Heroku: VC funded * Blake Mizerany from sinatra EY: * Ezra Zygmuntowicz * Yehuda Katz * Carl Lerche...
- #10: Choose the vendor that will fulfill your requirement the best (incl. cost and time to market). You must be able to switch each component from the OS to the caching middleware, from Linux to Varnish and Toky Cabinet.