Globaldev Tech Talk: Build your own Heroku

Globaldev Tech Talk: Build your own Heroku

The globaldev team is gradually becoming more polyglot, and is constantly
churning out more supporting applications to help run our platform. Deploying
all these apps the "old fashioned way" provides a big headache for our
Operations team. Luckily, the industry is moving more and more towards
containerised PaaS-style deployment such as that used by Heroku.

In this talk I discuss how companies that aren't on the absolute bleeding edge
of the Linux kernel can still leverage these patterns on their private
infrastructure, even when fantastic projects like Docker won't run on their
hardware. I also provide a preview of the technology that will be backing
Griddle when it is released. Let me know your thoughts in the comments below.

Ff870982e84d7f6dd6e1af91ab4e3797?s=128

Paul Bowsher

August 12, 2013
Tweet

Transcript

  1. Build Your Own Heroku Even if you run a 7-year-old

    Operating System* *title bait Friday, 4 April 14
  2. What makes a Heroku app a Heroku app? Friday, 4

    April 14
  3. Heroku App = 12 Factor App Friday, 4 April 14

  4. 1. Codebase 2. Dependencies 3. Config 4. Backing Services 5.

    Build, release, run 6. Processes 7. Port binding 8. Concurrency 9. Disposability 10.Dev/prod parity 11. Logs 12. Admin processes http://12factor.net/ Friday, 4 April 14
  5. How does Heroku work? Friday, 4 April 14

  6. Standard Base Platform Ubuntu 10.04 LTS Friday, 4 April 14

  7. Buildpacks Friday, 4 April 14

  8. Procfile Friday, 4 April 14

  9. Process Separation Friday, 4 April 14

  10. Why our own Heroku? Friday, 4 April 14

  11. Polyglot team CF, Java, Ruby, Node.js, Elixir, Go, Python Friday,

    4 April 14
  12. 35 apps in production +6 in last 4 months 2

    in development Friday, 4 April 14
  13. Operations headache Friday, 4 April 14

  14. DevOps More than just awesome GIFs http://devopsreactions.tumblr.com/post/56227454839/plan-deploy-aaaand-win Friday, 4 April

    14
  15. Contractual Config MYSQL_CORE_READ_HOST MYSQL_INBOX_WRITE_USER REDIS_HOST Friday, 4 April 14

  16. Standardised startup Friday, 4 April 14

  17. Standardised logging Friday, 4 April 14

  18. Zero install* Friday, 4 April 14

  19. DEMO Friday, 4 April 14

  20. Questions? Friday, 4 April 14