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.
VS
No	
  Step	
  1


$	
  git	
  push	
  heroku	
  master
New	
  features	
  drive	
  complexity
Simplicity	
  drives	
  separation
tl;dr
Memcached	
  as	
  a	
  cloud	
  
     service?
PING google.com (66.102.7.99): 56 data bytes
64 bytes from 66.102.7.99: icmp_seq=0 ttl=54 time=27.002 ms
64 bytes from 66....
PING 2.2.2.2 (2.2.2.2)   56(84) bytes of data.
64 bytes from 2.2.2.2:   icmp_seq=1 ttl=61 time=0.436 ms
64 bytes from 2.2....
20 - 150X Faster
PING 2.2.2.2 (2.2.2.2)   56(84) bytes of data.
64 bytes from 2.2.2.2:   icmp_seq=1 ttl=61 time=0.436 ms
64 bytes from 2.2....
Anything can be a cloud
       service*
Don’t underestimate the
 value of cloud service
People will pay
Make as easy to use as
      possible.
Then make it easier
You don’t need to do
     everything
Work with other cloud
      services
Cloud Keiretsu FTW
Oren	
  Teich	
  -­‐	
  @teich
  oren@heroku.com
  http://heroku.com
Cloud Services - Social App Workshop - Heroku - 2010-07-24
Cloud Services - Social App Workshop - Heroku - 2010-07-24
Cloud Services - Social App Workshop - Heroku - 2010-07-24
Cloud Services - Social App Workshop - Heroku - 2010-07-24
Cloud Services - Social App Workshop - Heroku - 2010-07-24
Upcoming SlideShare
Loading in …5
×

Cloud Services - Social App Workshop - Heroku - 2010-07-24

1,293 views

Published on

Overview of how a maniacal focus and new IaaS powered latencies enables anything to be a cloud service.

Published in: Technology
  • Be the first to comment

Cloud Services - Social App Workshop - Heroku - 2010-07-24

  1. 1. VS
  2. 2. No  Step  1 $  git  push  heroku  master
  3. 3. New  features  drive  complexity
  4. 4. Simplicity  drives  separation
  5. 5. tl;dr
  6. 6. Memcached  as  a  cloud   service?
  7. 7. PING google.com (66.102.7.99): 56 data bytes 64 bytes from 66.102.7.99: icmp_seq=0 ttl=54 time=27.002 ms 64 bytes from 66.102.7.99: icmp_seq=1 ttl=54 time=36.446 ms 64 bytes from 66.102.7.99: icmp_seq=2 ttl=54 time=25.828 ms PING pingtest.net (69.17.117.207): 56 data bytes 64 bytes from 69.17.117.207: icmp_seq=0 ttl=48 time=71.158 ms 64 bytes from 69.17.117.207: icmp_seq=1 ttl=48 time=72.828 ms 64 bytes from 69.17.117.207: icmp_seq=2 ttl=48 time=89.200 ms
  8. 8. PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data. 64 bytes from 2.2.2.2: icmp_seq=1 ttl=61 time=0.436 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=61 time=0.548 ms PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=1.94 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=1.90 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=2.01 ms
  9. 9. 20 - 150X Faster
  10. 10. PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data. 64 bytes from 2.2.2.2: icmp_seq=1 ttl=61 time=0.436 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=61 time=0.548 ms PING 192.168.1.7 (192.168.1.7): 56 data bytes 64 bytes from 192.168.1.7: icmp_seq=0 ttl=64 time=1.111 ms 64 bytes from 192.168.1.7: icmp_seq=1 ttl=64 time=0.574 ms 64 bytes from 192.168.1.7: icmp_seq=2 ttl=64 time=0.553 ms
  11. 11. Anything can be a cloud service*
  12. 12. Don’t underestimate the value of cloud service
  13. 13. People will pay
  14. 14. Make as easy to use as possible.
  15. 15. Then make it easier
  16. 16. You don’t need to do everything
  17. 17. Work with other cloud services
  18. 18. Cloud Keiretsu FTW
  19. 19. Oren  Teich  -­‐  @teich oren@heroku.com http://heroku.com

×