• Like
  • Save
AWS Customer Presentation - Podango
Upcoming SlideShare
Loading in...5

AWS Customer Presentation - Podango

Uploaded on

JT Zemp, CTO of Podango presents at the AWS Start-Up Event - Salt Lake City.

JT Zemp, CTO of Podango presents at the AWS Start-Up Event - Salt Lake City.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Podango on AWS
    • Architecture for Rich Media Application Platform to achieve Deep Brand Engagement
    • in a Web 2.0 world
  • 2.
    • Deep Brand Engagement
    • Show producers need to cater to their audiences where they are, in the way that they are accustomed to–not in a walled garden, or a destination site.
    • Rich Media Application Platform (RMAP)
  • 3. Deep Brand Engagement
    • Uniting brands, show producers, and audiences to create engagement and interaction around brands.
    • Dixie and MommyCast Survey says: MommyCast listeners 70% more likely to buy Dixie paper products
    • What does that mean for the technology? Distributed, audience-centric, loosely coupled
  • 4. DBE Map
  • 5. RMAP
    • RMAP = lots of media files
    • Lots of storage capacity and ability to grow
    • CPU time for transcoding, media assembly (ad/sponsorship and component stitching)
    • Traffic patterns are ‘spikey’
  • 6. Technology Map
  • 7. Media Processing
    • RSS ingestion
      • Pull media producers’ feeds & create episodes
    • Media transcoding and stitching
      • listen on SQS queue for jobs, pull originals off S3, process and pushed finished files to S3
  • 8. Content Publishing
    • ~16 Download Server EC2 instances
      • Proxy requests for S3
      • Can failover to CDN or S3 directly (bypassing proxy)
    • 3 HTTP load balancer instances
    • ~17 HTTP application server instances
      • HTML
      • RSS
    • 2 Image application server instances
  • 9. ROI - ROFL
    • Colo solution (Competitors)
      • Start: $100k+, 3-4 FTE management, ~$10k/mo
      • Now: 2-3 FTE, ~$100k/mo
    • AWS solution (smooth scaling)
      • Start: $0 setup, 1.5 FTE management, ~$1k/mo
      • Now: 1.5 FTE management
  • 10. Extensions into Business
    • AWS-inspired business practices
      • Distributed offices
      • On-demand staff augmentation
      • Low-risk, high quality communication
      • Flexible and fast, nimble and nascent
  • 11. Contact Info JT Zemp CTO www.podango.com [email_address] twitter.com/jt zemp