Building a cloud-friendly application
summary
Argues that cloud‑friendly apps keep developer code read‑only and user content writable and separate, produce a built artifact via composer/Sass that is deployed read‑only, and sync real data back to dev. Recommends use environment variables and small glue code to map host‑specific service formats into framework expectations (Symfony, Laravel), avoid writing credentials to disk, prefer a clustered application monolith over microservices for most PHP projects, and notes PHP 7.4 preloading can cut CPU ~20% while trading memory.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:10Larry Garfield
- 1:43What Is Cloud Computing
- 3:42What Makes an Application Cloud Friendly
- 4:16Split Your Code from Your Content
- 10:09The Drupal Configuration Management System
- 11:20What Happens at Runtime Stays at Runtime
- 13:33Database Credentials
- 17:45What Does that Glue Code Look like
- 19:46Laravel
- 21:20Local Development
- 36:58Drawbacks
related talks
20mBuilding a cloud-friendly application
01h 00mBuilding a cloud friendly application
27mThe Future of PHP Is In The Clouds
40mFrameworkless – The New Black?
18mMy Take on PHP
35mTwelve‑factor app for PHP applications: how to become cloud native
39mKeynote: Symfony without the Framework Bundle
02h 37mSymfony 4 best practices (Part 2)