Cloud Services - Gluecon 2010

630 views

Published on

How anything can be a cloud service.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
630
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide


  • our values are machette
    this preso about our values, and how that drove our architecture and some ideas on combining our values with the changes happening in cloud
  • Today this seems obvious, but at the start it was crazy talk. Starting with values of incredibly tight workflow meant git, lead to this crazy idea with git


  • we addressed this by splitting everything into it’s own component. And when we did that, we realized that that pattern opens up the ability for anyone else to provide a component as well
  • FFMPEG ami.
    Went after the simple angle.
    New Bamboo put together an ami providing fully curated stack


  • monetization strategy too.
    Too be fair, this is a model that’s been around for years. There is a new change though.






  • * on the same IaaS
  • running stuff is hard. People will pay for it.

  • running stuff is hard. People will pay for it.
  • running stuff is hard. People will pay for it.
  • running stuff is hard. People will pay for it.
  • running stuff is hard. People will pay for it.
  • running stuff is hard. People will pay for it.


  • Cloud Services - Gluecon 2010

    1. 1. Oren Teich @teich
    2. 2. VS
    3. 3. No Step 1 $ git push heroku master
    4. 4. New features drive complexity
    5. 5. Simplicity drives separation
    6. 6. Base Services Add-ons DNS Email Full-text Search Routing Mesh Perf Mgmt Shared DB Dyno Grid DB Worker Grid Memcached Deploy Developer API Partner Tools CLI Web API
    7. 7. tl;dr
    8. 8. Memcached as a cloud service?
    9. 9. 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
    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 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
    11. 11. 20 - 150X Faster
    12. 12. 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
    13. 13. Anything can be a cloud service*
    14. 14. Don’t underestimate the value of cloud service
    15. 15. People will pay
    16. 16. Make as easy to use as possible.
    17. 17. Then make it easier
    18. 18. You don’t need to do everything
    19. 19. Work with other cloud services
    20. 20. Cloud Keiretsu FTW
    21. 21. Oren Teich - @teich oren@heroku.com http://heroku.com
    22. 22. Apigee

    ×