Ruby in the Clouds

Software Architect at Evome
Apr. 18, 2010
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
Ruby in the Clouds
1 of 11

More Related Content

What's hot

Aws summit 2019   running kubernetesAws summit 2019   running kubernetes
Aws summit 2019 running kubernetesAdam Hamsik
AWS Customer Presentation - ZyngaAWS Customer Presentation - Zynga
AWS Customer Presentation - ZyngaAmazon Web Services
SpringOne Tour St. Louis - Serverless SpringSpringOne Tour St. Louis - Serverless Spring
SpringOne Tour St. Louis - Serverless SpringVMware Tanzu
Amazon web services: A Quick Introduction from CloudreachAmazon web services: A Quick Introduction from Cloudreach
Amazon web services: A Quick Introduction from Cloudreachcloudreachslideshare
Real World AWS Deployment With Boto, Fabric, and Cloud FormationReal World AWS Deployment With Boto, Fabric, and Cloud Formation
Real World AWS Deployment With Boto, Fabric, and Cloud FormationDixon Whitmire
AWS Customer Presentation - JovianDATAAWS Customer Presentation - JovianDATA
AWS Customer Presentation - JovianDATAAmazon Web Services

Viewers also liked

20151028 sociale media in de kinderopvang20151028 sociale media in de kinderopvang
20151028 sociale media in de kinderopvangI Like Media
Landry byers maria cannistra production managerLandry byers maria cannistra production manager
Landry byers maria cannistra production managerLandry Byers
Marcy's cover letterMarcy's cover letter
Marcy's cover letteringrid alexander
20160108 mailchimp20160108 mailchimp
20160108 mailchimpI Like Media
Umrah presentation by Qasim AliUmrah presentation by Qasim Ali
Umrah presentation by Qasim AliQasimAli1231
Sharanraj QA _ ResumeSharanraj QA _ Resume
Sharanraj QA _ ResumeSharan Raj

Similar to Ruby in the Clouds

Map Reduce along with Amazon EMRMap Reduce along with Amazon EMR
Map Reduce along with Amazon EMRABC Talks
Serverless architectureServerless architecture
Serverless architectureShubham_Indrawat
Stratos and PaaS for London Java CommunityStratos and PaaS for London Java Community
Stratos and PaaS for London Java CommunityPaul Fremantle
Serverless ArchitectureServerless Architecture
Serverless ArchitectureRajind Ruparathna
Fowa Miami 09 Cloud Computing WorkshopFowa Miami 09 Cloud Computing Workshop
Fowa Miami 09 Cloud Computing WorkshopMark Masterson
Building Serverless Microservices Using Serverless Framework on the CloudBuilding Serverless Microservices Using Serverless Framework on the Cloud
Building Serverless Microservices Using Serverless Framework on the CloudSrini Karlekar

Similar to Ruby in the Clouds(20)

Ruby in the Clouds

Editor's Notes

  1. 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.
  2. The focus is given on what's essential: the application, not on "how to host and monitor it". 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, ...)
  3. 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.
  4. Choose one of the best player: Heroku: VC funded * Blake Mizerany from sinatra EY: * Ezra Zygmuntowicz * Yehuda Katz * Carl Lerche...
  5. 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.