How Serverless Transforms PHP Development: From LAMP to Elastic FaaS

Background

PHP powers more than 244 million websites and accounts for about 78.9% of web servers. Traditional LAMP or LNMP deployments require manual installation, configuration, and ongoing maintenance of the full stack on every server.

Serverless concept

Serverless combines Function‑as‑a‑Service (FaaS) and Backend‑as‑a‑Service (BaaS). The cloud platform provisions resources, scales automatically, and charges per invocation, allowing developers to focus solely on business logic.

Alibaba Cloud Function Compute Custom Runtime for PHP

Alibaba Cloud Function Compute provides a Linux environment with built‑in nginx/1.10.3 and php-fpm7.4. When a function is invoked, the platform runs a bootstrap script that starts php‑fpm and nginx, exposing a custom HTTP server that handles all incoming requests.

Deploying a PHP application (WordPress example)

Package the following files into a zip archive and create a Function Compute function:

- bootstrap
- nginx.conf
- php-fpm.conf
- php.ini-production
- wordpress/

Sample bootstrap script (make it executable):

#!/bin/sh

echo "start php-fpm"
php-fpm7.4 -c /code/php.ini-production -y /code/php-fpm.conf

echo "start nginx"
nginx -c /code/nginx.conf

Handling persistence

Function Compute is stateless. Persistent data such as uploaded files or session data should be stored in external services (e.g., NAS, Redis). Mount a NAS directory to the function instance and configure nginx.conf to serve the web root from the mounted path.

Reference implementations

Serverless starter projects for ThinkPHP, Laravel, WordPress, and Z‑BlogPHP are available in the GitHub repository https://github.com/devsapp/start-web-framework.

Custom Runtime documentation: https://help.aliyun.com/document_detail/132044.html.

WordPress‑specific bootstrap example:

https://github.com/devsapp/start-web-framework/blob/master/web-framework/php/wordpress/src/code/bootstrap

.

Key advantages of PHP on Function Compute

Developers write only application code; no server provisioning or OS patching.

Automatic elastic scaling eliminates manual load‑balancing and capacity planning.

Pay‑as‑you‑go pricing measured in milliseconds reduces cost for low‑traffic workloads.