Jeff Lindsay: Building Public Infrastructure with Autosustainable Services

723 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
723
On SlideShare
0
From Embeds
0
Number of Embeds
89
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Jeff Lindsay: Building Public Infrastructure with Autosustainable Services

  1. 1. Autosustainable Services Jeff Lindsay @progrium
  2. 2. 1. Public Infrastructure2. Autosustainable Services3. Airscript Demo
  3. 3. 1. Public Infrastructure2. Autosustainable Services3. Airscript Demo
  4. 4. WARNINGThis talk contains big ideas and is not really specific to Python at all
  5. 5. Throwing Together Distributed Services with geventhttp://www.youtube.com/watch?v=tYk4_Nzl-Gg
  6. 6. Distributed Systems with ZeroMQ and geventhttp://www.infoq.com/presentations/Distributed-Systems-with-ZeroMQ-and-gevent
  7. 7. Web APIClient TwiML
  8. 8. Distributed Systems
  9. 9. Distributed Systems Internal System
  10. 10. Distributed Systems External Ecosystem Internal System
  11. 11. Distributed Systems External Ecosystem Macro level Internal System Micro level
  12. 12. Data
  13. 13. Data Communications
  14. 14. OperationsData Communications
  15. 15. OperationsData Real world Communications
  16. 16. Operations DataEverything as a Service Real world Communications
  17. 17. What I want is to...
  18. 18. What I want is to... Program the World
  19. 19. xargs wget echo mailgrep wc cat
  20. 20. cat xargs wget echo mailgrep wc
  21. 21. cat grep xargs wgetecho mail wc
  22. 22. cat grep mail xargs wgetecho wc
  23. 23. More ComposableWebhooks and “Evented Web”
  24. 24. More ComposableWebhooks and “Evented Web”
  25. 25. More ComposableWebhooks and “Evented Web”
  26. 26. More ComposableWebhooks and “Evented Web”
  27. 27. More ComposableWebhooks and “Evented Web”
  28. 28. RequestBinhttp://requestb.in
  29. 29. Localtunnelhttp://localtunnel.com
  30. 30. Smaller PiecesTiny Apps and Micro APIs
  31. 31. Smaller PiecesTiny Apps and Micro APIs
  32. 32. Smaller PiecesTiny Apps and Micro APIs
  33. 33. stdiconhttp://stdicon.com
  34. 34. TimeAPIhttp://timeapi.org
  35. 35. Why aren’t there more?
  36. 36. Why aren’t there more? Economics
  37. 37. MailHookshttp://mailhooks.com
  38. 38. MailHookshttp://mailhooks.com
  39. 39. Twitter Hookshttp://twitterhooks.com
  40. 40. JabberHookshttp://jabberhooks.com
  41. 41. PostBinhttp://postbin.org
  42. 42. ClickHookshttp://clickhooks.com
  43. 43. Scriptletshttp://scriptlets.org
  44. 44. App Engine
  45. 45. Open Source
  46. 46. Open SourceMajority are tools and libraries
  47. 47. Project
  48. 48. Project
  49. 49. Project
  50. 50. ProjectProject
  51. 51. ProjectProject
  52. 52. ProjectProject
  53. 53. ProjectProjectProject
  54. 54. Web ServicesMore leverage, more power
  55. 55. Software has open source.SaaS has no equivalent...
  56. 56. Why?
  57. 57. Why?Operations and Cost
  58. 58. Solution:
  59. 59. Solution:Autosustainable Services
  60. 60. Operations
  61. 61. Operations• Use PaaS, embrace NoOps / DevOps
  62. 62. Operations• Use PaaS, embrace NoOps / DevOps• Design for simplicity and scalability
  63. 63. Operations• Use PaaS, embrace NoOps / DevOps• Design for simplicity and scalability• Aggressively avoid state
  64. 64. Operations• Use PaaS, embrace NoOps / DevOps• Design for simplicity and scalability• Aggressively avoid state• Automate maintenance tasks
  65. 65. Operations• Use PaaS, embrace NoOps / DevOps• Design for simplicity and scalability• Aggressively avoid state• Automate maintenance tasks• Make metrics public
  66. 66. Operations• Use PaaS, embrace NoOps / DevOps• Design for simplicity and scalability• Aggressively avoid state• Automate maintenance tasks• Make metrics public• Give deploy access to maintainers
  67. 67. Cost
  68. 68. Cost• Leverage volunteer community
  69. 69. Cost• Leverage volunteer community• Use cloud and/or PaaS services
  70. 70. Cost• Leverage volunteer community• Use cloud and/or PaaS services• Design to minimize resources usage
  71. 71. Donations
  72. 72. Donations with a twist
  73. 73. Donations with a twist• Automated, ongoing fundraising
  74. 74. Donations with a twist• Automated, ongoing fundraising• Calculate cost to run in real-time
  75. 75. Donations with a twist• Automated, ongoing fundraising• Calculate cost to run in real-time• Know dollar amount in funding source
  76. 76. Donations with a twist• Automated, ongoing fundraising• Calculate cost to run in real-time• Know dollar amount in funding source• Show users how long it will survive
  77. 77. Donations with a twist• Automated, ongoing fundraising• Calculate cost to run in real-time• Know dollar amount in funding source• Show users how long it will survive• Remove yourself from funding path
  78. 78. This service can run for 132 more days. $10 Donate
  79. 79. This service can run for 60 more days. $20 Donate
  80. 80. Service shutting down in 10 days without your support $30 Donate
  81. 81. This service can run for 132 more days. $10 Donate
  82. 82. What does this get us?
  83. 83. Service
  84. 84. Service
  85. 85. Service
  86. 86. ServiceService
  87. 87. ServiceService
  88. 88. ServiceService
  89. 89. ServiceServiceService
  90. 90. ServiceServiceService
  91. 91. ServiceServiceService
  92. 92. No economic friction to building small, composable services
  93. 93. Program the World
  94. 94. Airscript Demo
  95. 95. Questions Jeff Lindsay @progrium

×