PHP runtime have been controversial for years; because hosting is very important due to dynamic and modularity of PHP. So, what’s about opcode cacher? atomic deployment? file system usage? session management? code/data split? PHP VM or built in http server? Or maybe HHVM? So many question we have to answer building php support at Clever Cloud (managing A LOT of php apps on hosting PaaS), and many war stories to share about our choices.
24. 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
25. SPLIT DATA AND
CODE
Data
• Databases
• Files
• Sessions
• Events
• …
Code
• Can be replicated
• Stateless
• Process