The document provides a brief introduction to Heroku PHP hosting, highlighting the benefits of using a Platform as a Service (PaaS) for managing web applications. It compares PaaS to Infrastructure as a Service (IaaS) and Software as a Service (SaaS), and discusses Heroku's capabilities, pricing structures for different project sizes, and the process of setting up and deploying a PHP application. The speaker, Olivier Garcia, emphasizes the ease of use, automation, and the need for caching solutions for larger applications.

1. a 10 MINUTES intro
to Heroku PHP hosting
a 10 MINUTES intro
to Heroku PHP hosting

2. So you made a
shiny new app
And you installed on
a dedicated server.

3. YOU MAY
HAVE ISSUES

4. Failing hardware
○ RAID drives down
○ Fan broken
○ Network card KO
○ Motherboard burnt
○ DDOS

5. Software to patch
○ PHP
○ Apache / Nginx
○ MySQL, MongoDB
○ Linux
○ Bash
○ OpenSSL
○ ...

6. Hi !
I am Olivier Garcia
I am here because I’ve been
through that before.
You can find me at:
@0livier

7. SOMETIMES, it’s better to
○ Delegate hardware & platform management
○ Focus on code & customers, not technical scaling

8. Platform As A Service
Run Web applications without building and
maintaining the infrastructure

9. PaaS
You’re given a repo
You push your code
e.g. Heroku, Azure
IaaS
You’re given a server
You install a Linux
e.g. OVH, AWS
Comparing /.+ as a Service/
SaaS
You’re given software
You use it
e.g. Gmail, Salesforce

10. Introducing
Heroku

11. Languages
○ PHP
○ JS
○ Go
○ Python
○ Java/Scale
○ Closure
and more !
Runs most of the OSS tech stack
DB
○ MySQL
○ PostgreSQL
○ MongoDB
○ Redis
○ Solr
○ Graphite
and more !

12. ○ Everything can be
done in CLI &
automated
Insanely easy to work with
○ Great documentation
○ Huge list of add-ons

13. Load balancing
Requests are load
balanced on all
nodes, no custom
rules can be made
When it’s is not the right solution
Custom components
It may take some
time/skills to add
special components
eg. mod_deflate for Apache
Size
Your app must hold
in 100MB

14. Caching
You may need
Varnish and a CDN
on top of your app
When it’s is not the right solution
No custom hardware
The only way to get
more RAM or CPU is
to buy new instances
Price
With a lot of traffic or
processing, the
hosting will get
expensive quickly

15. Some cost
examples

16. Toy projects
0 $
○ CPU: 1 core
○ RAM: 512Mo
○ DB: 64GB
○ Support by mail : 1+ day

17. Small projects
○ CPU: 8 cores
○ RAM: 6 Go
○ DB: 64 GB
○ Custom SSL Domain
○ Support by mail : 1+ day
770 $

18. Big projects
○ CPU: 4 x 8 cores
○ RAM: 4 x 6 Go
○ DB: 1 TB
○ Custom SSL Domain
○ Support in 1H
5220 $

19. DEMO
I previously
○ Created an account
○ Installed the heroku pkg

20. DEMO FALLBACK
Well, it’s not working as
planned, let’s fall back on
slides...

21. Setup project
$ mkdir -p ~/Code/heroku-demo/web
$ cd ~/Code/heroku-demo
$ git init .
$ heroku create php-10m-demo

22. composer.json
{
"require" : {
},
"require-dev": {
"heroku/heroku-buildpack-php": "*"
}
}

23. Procfile
web: vendor/bin/heroku-php-apache2 web/

24. web/index.php
<?php
phpinfo();

25. Add files to project
$ git add web Procfile composer.json
$ git commit -m “Added: Project files”

26. Deploy !
$ git push heroku master

27. See the deployed app
$ heroku open

28. Scale up & down
$ heroku ps:scale web=10
$ heroku ps:scale web=1
$ heroku ps:scale web=0

29. Get logs & run command
$ heroku logs
$ heroku run bash
$ heroku run app/console cache:clear

30. THANKS!
Any questions?
You can find me at:
@0livier (with a zero not a o)
olivier@lol.cat

31. CREDITS
Special thanks to all the people who made and
released these awesome resources:
○ Various GIF from reactiongifs.com and gif.lol.cat
○ Presentation template by SlidesCarnival
○ Photographs by Unsplash