Launching the Serverless PHP newsletter
Serverless is a topic that is getting more and more attention lately. While this is exciting, it also means there is a lot to follow, read and test.
I have met several people who are interested about serverless and its possibilities but have a lot of trouble following everything. This is even more true in the PHP ecosystem because PHP was initially left out from AWS Lambda and other FaaS products.
In order to help I have started a monthly newsletter called Serverless PHP news.
This newsletter will contain an overview of what's new regarding serverless and how it relates to PHP. Because some news are worth knowing about only if you can relate it to the tools you are using everyday.
If you are interested, go subscribe at:
To give you an idea what to expect you can find below a copy of the first email.
Serverless PHP #1: The state of serverless PHP
Welcome to the first issue of the Serverless PHP newsletter.
First of all I want to wish you a happy new year, and thank you so much. You are more than 400 subscribed to this list and I definitely did not expect that. I hope this newsletter will live up to your expectations and I welcome any feedback (really!).
This episode is the first so I will sum up the current state of serverless PHP and talk about the main event of the last months: AWS re:Invent.
If you don't know anything about "Serverless" you can read an introduction in Martin Fowler's serverless bliki entry or Serverless and PHP: introducing Bref.
Before AWS re:Invent
AWS re:Invent is a conference held annualy by AWS. This year (November 2018) it changed a lot of things, so let's start by a recap of how PHP ran on AWS Lambda before.
Since PHP was not officially supported on AWS Lambda the only way to run PHP was to:
- compile PHP and include the binary in the lambda
- include our PHP script (or application) in the lambda as well
That worked fine but this had an impact on performances. Compiling PHP and writing the JS proxy script was also impractical, which is why Bref was created in the first place and this is what the current version (v0.2) is about. This is going to change!
My selection of what was announced in November by AWS that may interest you:
- Use any programming language on AWS Lambda thanks to "lambda layers" and an "open runtime" API (explained in more details in the next section)
- Cold start improvements when using RDS: RDS is MySQL/PostgreSQL managed by AWS. Using those with Lambda works fine except it requires to put the lambda and the database in the same VPC (private virtual network). This implies a cold start of about 5 to 10 seconds, which is a huge pain for HTTP applications. This will be solved in 2019 which, I believe, is very very good news!
- RDS makes MySQL and PostgreSQL accessible via a HTTP API: this is interesting because it allows to skip managing persistent SQL connections and it is much more in line with the serverless paradigm (it is stateless). However the first version released by Amazon is definitely not ready for production right now. AWS is known for releasing alpha services and continuously improving them so let's be patient and keep an eye on it!
- Announcing Firecracker, the "micro-VM" alternative to containers and virtual machines developped by AWS to run AWS Lambda. Their goal: the security of VMs and the low costs (startup time and overhead) of containers. You don't need to learn about this as AWS takes care of the details, but it is interesting to know why they are not using containers.
- AWS SAM has received a lot of new features which makes it a very serious alternative to the serverless framework for deployments. AWS SAM is restricted to AWS but comes with very useful development tools running on Docker.
- DynamoDB goes full serverless via a new "pay per request" pricing: no need to reserve capacity, DynamoDB can now behave just like AWS Lambda: we can pay per request and it will scale on demand automatically.
- DynamoDB gets transactions support for those interested in replacing their database with DynamoDB. The new API seems limited but it may help in some scenarios.
- IntelliJ plugin to run and debug serverless applications: this will be interesting for PhpStorm users (the plugin seems to be usable only in IntelliJ for now, let's keep an eye on this)
- ALB as an alternative to API Gateway for HTTP lambdas. ALB is Amazon's Application Load Balancer and it can now be used to expose Lambdas on the web without having to use API Gateway. ALB is much simpler as there is no routes to define: it proxies everything to the lambda, and it is supposedly faster as well. There is also a difference in pricing: there is a minimum of $22 per month for ALB where API Gateway starts at $0. However for bigger applications ALB is cheaper. If you are writing websites or APIs on Lambda and pay more than $22 per month on API Gateway it may be worth investigating! Remember to share your experience!
All the re:Invent talks are online on Youtube. I can recommend this talk about DynamoDB which was very enlightening for me about NoSQL in general and DynamoDB itself. I am tempted to try and rewrite externals.io using Lambda and DynamoDB to learn a bit more about it (hopefully in the coming months).
PHP on AWS Lambda
Now that we have an official way to run PHP on AWS Lambda, let's look at how it works. The idea is that lambdas can now use layers. A layer is a bunch of files that will be injected in the lambda when it starts.
We can add support for PHP in AWS Lambda by creating a layer that injects the
php binary in the lambda. But that is not enough: we need a
bootstrap is the file that is called when the lambda starts. It is responsible for executing the PHP script whenever there is a new event. What's great is that the
bootstrap file can be written in any language, including PHP.
AWS announced that a company called Stackery worked on a PHP runtime: github.com/stackery/php-lambda-layer. However this runtime is definitely not ready for production and I found it very disappointing on several levels (I am not alone to think this).
With Bref contributors we have benchmarked several solutions for running PHP on Lambda. Those include running PHP scripts as well as HTTP applications using PHP-FPM or even PHP's built-in webserver. We have identified the best solutions and we have begun porting them in the new version of Bref.
The vision for Bref has not changed: it is not just about PHP support, it is about empowering everyone to benefit from serverless technologies. We are hard at work on the next version (v0.3) which will provide:
- stable PHP runtimes for PHP functions as well as HTTP and console applications
- much better performances thanks to these native runtimes
- a completely rewritten and extensive documentation
- a revisited deployment process that integrates with AWS tooling
- tools for local development based on Docker (thanks to AWS SAM)
- support for any PHP application or framework thanks to PHP-FPM and the console runtime
If you are interested you can follow the v0.3 pull request that summarizes all changes.
PHP outside AWS
Zeit.co has basic support for PHP but I wouldn't consider it production-ready: it supports only 1 PHP file per application and runs it via
go-php, a PHP 7 implementation in Go. Hopefully this will improve in the future.
IBM OpenWhisk is interesting as it can run Docker containers (so it can run PHP applications). Finally an interesting alternative that may be worth exploring is Alibaba Cloud which supports PHP functions as well as PSR-7 requests for HTTP applications.
My personal belief is that AWS is years ahead of its competitors right now, especially after the latest announcements. AWS Lambda is also very stable and reliable compared to Google Functions and Azure Functions. Let's see how things evolve in the next months and years!
That's it! This first episode is quite packed but a lot has been happening lately. I hope it helps you get a better overview of all this.
If you are interested in exploring the serverless world for your next big thing I hope that all of this will be useful. If you need someone to help feel free to get in touch.