Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AWS Customer Presentation - Podango


Published on

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

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

AWS Customer Presentation - Podango

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