Building on Twitter

  • 1,142 views
Uploaded on

How we first built tweetmeme.com in one weekend. Nearly a year later we rebuild the site with API and widgets. The slides show the costs and the impact on running a more complex and much more costly …

How we first built tweetmeme.com in one weekend. Nearly a year later we rebuild the site with API and widgets. The slides show the costs and the impact on running a more complex and much more costly website.

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

Views

Total Views
1,142
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
9
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide












































Transcript

  • 1. NICK HALSTEAD Founder & CEO twitter.com/nickhalstead #INTRO
  • 2. DEVELOPMENT BUSINESS THE FUTURE #TOPICS
  • 3. FIRST A QUICK STORY (TRY NOT TO NOD OFF) #STORY
  • 4. (LAST YEAR) BUILDING WEB 2.0 IN 16 HOURS #BUILDING
  • 5. HAVE AN IDEA #IDEA
  • 6. GET A GOOD CODER #BABY
  • 7. GET A DESIGNER (my designer @DTSN supplied this picture of himself) #MONKEY
  • 8. INSERT COKE #COKE
  • 9. DO SOME WORK #POO
  • 10. INSERT PIZZA #PIZZA #YUMMY
  • 11. DO MORE WORK #MOREPOO
  • 12. INSERT MORE JUNK #COKE+PIZZA
  • 13. CRUNCH TIME #BUZZING
  • 14. LAUNCH PRODUCT! • TWITTER AGGEGRATOR • LOOKS FOR LINKS TO CONTENT • DISPLAYS MOST POPULAR CONTENT • CATEGORISES THE CONTENT #LAUNCH
  • 15. WHAT IT COSTS (LAST YEAR) • £500 for contract programmer • 4 hours internal design time • 4 hours (me programming) • total man hours = 16 #COSTS
  • 16. WHAT IT COSTS (LAST YEAR) • £500 for contract programmer • 4 hours internal design time RETURN TO THIS LATER...... • 4 hours (me programming) • total man hours = 16 #COSTS
  • 17. DEVELOPMENT #DEVELOPMENT
  • 18. THE ‘FIREHOSE’ (public timeline) #SCARY
  • 19. THE ‘FIREHOSE’ TWEETS READY FOR GROWTH? #LOTS #AND #LOTS
  • 20. THE ‘FIREHOSE’ TWEETS #LOTS
  • 21. THE ‘FIREHOSE’ TWEETS 800,000+ a day #LOTS
  • 22. THE ‘FIREHOSE’ TWEETS 800,000+ a day 24 million a month #LOTS
  • 23. THE ‘FIREHOSE’ TWEETS 800,000+ a day 24 million a month = year #LOTS
  • 24. THE ‘FIREHOSE’ TWEETS 1200%+ GROWTH IN LAST 12 MONTHS #COSTL Y
  • 25. THE ‘FIREHOSE’ TWEETS 1200%+ GROWTH IN LAST 12 MONTHS 2010 288 million a month? #COSTL Y
  • 26. THE ‘FIREHOSE’ TWEETS 1200%+ GROWTH IN LAST 12 MONTHS 2010 288 million a month? = month #COSTL Y
  • 27. THE ‘FIREHOSE’ ACCESS Data Mining Feed #FIREHOSE
  • 28. THE ‘FIREHOSE’ ACCESS Data Mining Feed stream HTTP (Q2 2009) #FIREHOSE
  • 29. THE ‘FIREHOSE’ ACCESS Data Mining Feed stream HTTP (Q2 2009) XMPP (been and gone...) #FIREHOSE
  • 30. THE ‘FIREHOSE’ ACCESS Data Mining Feed stream HTTP (Q2 2009) XMPP (been and gone...) 3rd Party (e.g. GNIP) #FIREHOSE
  • 31. WHITELISTING 20,000 requests per hour http://twitter.com/help/request_whitelisting #WHITELIST
  • 32. OPTIMIZATION DB DE-NORMALIZATION STATIC CONTENT MEMCACHE CLOUD? #SPEED
  • 33. OPTIMIZATION Speed != Scalable #SPEED
  • 34. BACK TO OUR STORY #STORY
  • 35. BEYOND BOOTSTRAP (THIS YEAR) #MORECOS T
  • 36. BEYOND BOOTSTRAP (THIS YEAR) Development • Monthly Updates • 10 days x 4 Team Members • total man hours = 320 • £10,000 a month #MORECOS T
  • 37. BEYOND BOOTSTRAP (THIS YEAR) Development Hosting • • Monthly Updates Bandwidth £500+ • 10 days x 4 Team • Dedicated Servers Members £1500+ month • total man hours = 320 • Cloud Computing • £10,000 a month • Maintenance #MORECOS T
  • 38. WHY INVEST THIS MUCH? #WHY
  • 39. BUSINESS #BUSINESS
  • 40. +BRANDS #BRANDS
  • 41. WHY? #QUESTION
  • 42. #QUESTION
  • 43. TRUST OPINION OF A FRIEND 83%!! WHO HAS USED THE PRODUCT #TRUST
  • 44. has made $1 million revenue on #DELL
  • 45. DEDICATED 20% OF PR BUDGET TO SOCIAL MEDIA #NETAPP
  • 46. Revenue Models Sponsorship / Advertising Promoting Twitter Accounts Engagement #REVEN UE
  • 47. FUTURE #AWESOME #GROWTH
  • 48. Technology is Hard to Predict “What scaling walls will Twitter hit? Obviously the technology scales pretty well, it's not using a whole lot of CPU” Dave Winer, March 2007 #FAIL
  • 49. What We Know... OAuth Integration/Purchase 3rd Party API/Products’s Start of Advertising
  • 50. #REAL #LIFE