• Save
AWS Customer Presentation - How Runa uses AWS
 

AWS Customer Presentation - How Runa uses AWS

on

  • 3,299 views

Robert Berger discusses how Runa uses AWS at the AWS Startup Tour - SV - 2010

Robert Berger discusses how Runa uses AWS at the AWS Startup Tour - SV - 2010

Statistics

Views

Total Views
3,299
Views on SlideShare
3,279
Embed Views
20

Actions

Likes
1
Downloads
0
Comments
0

2 Embeds 20

http://www.slideshare.net 19
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

AWS Customer Presentation - How Runa uses AWS AWS Customer Presentation - How Runa uses AWS Presentation Transcript

  • Runa on AWS
    Big Data & Machine Intelligence for a SaaS Startup
  • Runa
  • aSaaS
  • convertsShoppers to Buyers
  • forOnline Commerce Sites
  • by presentingDynamic Personalized Promotions
  • on theMerchant’s Website
  • inReal-Time
  • in the Shopping Flow
  • Tech Challenges
  • Big Data
  • JavaScript client collects activity on every Merchant page for every Shopper
  • One or more Ajax call & Event Store to Runa per Merchant page view
  • Step function increase of calls and stores as each new Merchant added
  • We capture everything we can and store it forever
  • Expecting to grow to thousands of merchants
  • That’s a lot of Data
  • Processing Data withMachine Intelligence
  • Batch Processing forStatistical Analysisand Reports
  • Real-Time Rule based inserts of Promotions
  • Tech Challenges Synopsis
    Big Data & Processing
    Step Function Growth
    Batch Processing
    Real-Time Promotions
  • Why AWS for Runa?
  • At First(a couple years ago)
  • Not Much Money in the Bank
  • Didn’t Know exactly what were making
  • Or exactly how we were going to do it
  • Prototyped with Ruby / Rails / MySQL
  • ThenPrototype became Production
  • EC2 & AWS let us scale the prototype to Beta Production
  • Flexibility to incrementally refine service & infrastructure
  • Confidence we could scale as we added Merchants
  • More RecentlyIncrementally added next-gen Tech & Full Production
  • Goal: Everything Horizontally Scalable
  • Batch Processing & Infinite StorageMap / Reduce& BigTable viaHadoop & HBase
  • Flexible Real-Timeparallel processingvia Clojure / Swarmiji
  • Deployment & Configuration ManagementviaOpscode Chef
  • Good Things
  • Able to Start Small
  • ThenGROW BIGGER
  • Having the flexibility to throw “Hardware” at our Prototype got us to market faster
  • Ability to launch test and staging environments almost at will
  • “Hardware” as “Software”
  • Living in “interesting” times
  • Managing Complexitylots of moving parts
  • Easy to launch a few instances
  • Impossible to manage horizontal stacks“by hand”
  • Must have tool like Opscode Chef
  • Chef automates deployment & puts it under Revision Control
  • There’s going to be some blood when using cutting edge tech
  • Lots of Learning Curves to climb
  • Useful Monitoring is hard but Critical
  • HBase on AWS may be dangerousbecause of Hadoop namenode SPOF
  • EC2 bill can surprise you if you cavalierly deploy multiple versions of horizontally scalable environments
  • Could not do our startup without AWS or lots more VC Funding