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 bytes64 bytes from 66.102.7.99: icmp_seq=0 ttl=54 time=27.002 ms64 bytes from 66.102.7.99: icmp_seq=1 ttl=54 time=36.446 ms64 bytes from 66.102.7.99: icmp_seq=2 ttl=54 time=25.828 ms

PING pingtest.net (69.17.117.207): 56 data bytes64 bytes from 69.17.117.207: icmp_seq=0 ttl=48 time=71.158 ms64 bytes from 69.17.117.207: icmp_seq=1 ttl=48 time=72.828 ms64 bytes from 69.17.117.207: icmp_seq=2 ttl=48 time=89.200 ms

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 ms64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms64 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 ms64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=1.90 ms64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=2.01 ms

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 ms64 bytes from 2.2.2.2: icmp_seq=2 ttl=61 time=0.630 ms64 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 bytes64 bytes from 192.168.1.7: icmp_seq=0 ttl=64 time=1.111 ms64 bytes from 192.168.1.7: icmp_seq=1 ttl=64 time=0.574 ms64 bytes from 192.168.1.7: icmp_seq=2 ttl=64 time=0.553 ms

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  -­‐  @teichoren@heroku.comhttp://heroku.com