PHP deploy 2015 flavor - talk from php tour 2015 luxembourg
Download as PPTX, PDF2 likes2,647 views
The document discusses the intricacies of deploying PHP applications, emphasizing best practices for managing data, code, and hosting solutions. It critiques traditional file systems as data stores, endorsing the use of various databases and event brokers for modularity and efficiency. The author advocates for stateless applications, automated deployment processes, and modern tools like Docker and Composer to streamline development.
PHP deploy 2015 flavor - talk from php tour 2015 luxembourg
- 1. DEPLOY SOME PHP APP 2015 FLAVOR QUENTIN ADAM @WAXZCE 2013
- 2. Quentin ADAM from the Clever Cloud @waxzce on twitter – github- soundcloud – instagram …. WHO AM I ?
- 3. MY DAY TO DAY WORK : CLEVER CLOUD, MAKE YOUR APP RUN ALL THE TIME
- 4. And learn a lot of things about your code, apps, and good/bad design… KEEP YOUR APPS ONLINE. MADE WITH NODE.JS, SCALA, JAVA, RUBY, PHP, PYTHON, GO…
- 5. AND LEARN A LOT OF THINGS ABOUT YOUR CODE, APPS, AND GOOD/BAD DESIGN…
- 6. PHP AS PERSONAL HOME PAGE
- 7. DISPLAY CONTENT ON WILD WIDE WEB
- 8. THEN DISPLAY DYNAMIC CONTENT
- 9. THEN LINK TO DATABASE
- 10. USE MOD_PHP AND EVERYTHING IS NOW ROOT
- 11. THE LAMP STACK IS BIRTH
- 12. AND SOME HOSTING PROVIDER CREATE THE SHARED HOSTING CHEAPEST WAY TO EXPOSE ON THE WEB
- 13. AND IT’S GREAT
- 14. THEN PEOPLE CREATE MORE AND MORE COMPLEX APPLICATIONS
- 15. AND WE FACE PROBLEM ABOUT HOSTING AND DEPLOYING
- 17. PHP GREATNESS: MANAGE THE REQUEST LIFE CYCLE
- 18. NO MUTABLE MADNESS INSIDE VARIABLE AND RAM
- 19. BUT QUITE OFTEN MIGRATED TO THE FILE SYSTEM
- 20. THE FILE SYSTEM
- 21. ACID ACID • Atomicity • Consistency • Isolation • Durability Powerful data management • Transaction • User management • One above one
- 22. BUT IT DESIGNS A BOTTLENECK
- 23. DO NOT USE THE FILE SYSTEM AS A DATASTORE File system are POSIX compliant • POSIX is ACID • POSIX is powerful but is a bottleneck • File System is the nightmare of ops • File System creates coupling (host provider/OS/language) • SPOF-free multi tenant File System is a unicorn STORE IN DATABASE, OR IN A DATASTORE LIKE S3/RIAKCS DEDICATED TO FILE MANAGEMENT
- 24. SPLIT DATA AND CODE Data • Databases • Files • Sessions • Events • … Code • Can be replicated • Stateless • Process
- 25. CONSIDER MORE THINGS AS DATA • User account • Users data • Files • Sessions • Events
- 27. CHOOSE YOUR DATASTORE WISELY YOU CAN SHOULD USE MANY DATASTORES
- 29. USE AN EVENT BROKER TO MODULARIZE YOUR APP
- 30. USE YOUR EVENT BROKER AS ASYNC MANAGER
- 31. USE AN EVENT BROKER TO MODULARIZE YOUR APP • AMQP • Celery • 0MQ • Redis • JMS • Even some http chunk or websocket • Some case : hadoop, akka… • …
- 32. CRON + FS IS NEITHER AN EVENT QUEUE NOR A JOB SCHEDULER
- 33. USE ONLINE DATABASE / BE READY TO TEST IN JUST A FEW MINUTES NO NEED TO TRASH YOUR COMPUTER
- 34. {P, DB, S} aaS USE OPS FREE SOLUTION TO LEARN AND START
- 35. LOGS
- 36. DO NOT USE THE FILE SYSTEM AS A DATASTORE : LOGS USE CASE
- 37. LOGS IN FILES I HATE IT
- 38. CDN for example MANAGE TO SERVE ASSETS FROM SOMEWHERE ELSE
- 39. THIS IS NOT BUNCH OF SCRIPTS, THIS IS APPLICATION
- 40. DO NOT GENERATE .PHP FILE AT RUN
- 41. FORGET ABOUT FTP, EMBRACE GIT
- 42. NEVER HOTFIX ON SERVER
- 43. USE BUILD SYSTEM, COMPOSER FTW COMPOSER IS THE LAST STANDING MEN
- 44. AND NEVER EDIT A SINGLE FILE FROM VENDOR/ 0_0
- 45. BTW NPM/GRUNT/BROWSERIFY WORK WELL FOR FRONT BUILD
- 46. DO NOT COMMIT AND SHIP DEPS
- 47. CAN YOU RUN WITHOUT WRITE PERM?
- 48. DEPLOY
- 49. THINK AT IT AS COMPILE TIME
- 50. BIANCA
- 51. HHVM
- 53. http://fr.slideshare.net/quentinadam/use-docker-as-the-operation-system-builder-doker-conference DOCKER AS AN OPERATING SYSTEM BUILDER
- 54. UNIX - LINUX PERMISSION
- 56. DO NOT CARE, RUN ALL ROOT
- 57. Partial isolation via vhost, weird hacks and setUid USE MOD ITK
- 58. USE CHROOT AND SUEXEC
- 59. Do not cross the flux FASTCGI – PHP-FPM
- 60. We don’t want to build history ALWAYS BE AT A CLEAN STATE OF THE SERVER/OS
- 61. Picking one instance or another doesn’t matter STATELESSNESS IS THE KEY
- 62. USE ENV
- 63. WORK OF DEVELOPER HAS TO STOP AT GIT PUSH
- 64. APPLICATIONS HAVE TO DEPLOY
- 65. AUTO INCREMENT
- 66. I’m @waxzce on twitter I’m the CEO of A PaaS provider, give it a try ;-) THX FOR LISTENING & QUESTIONS TIME