Since AWS lambda supports custom runtimes you can use PHP to create AWS lambda functions.\nBut it comes with two major drawbacks
\nWith bref.sh these problems will disappear. Let's try to run Symfony framework as a serverless app.
\nWhat does it mean that something is Serverless? Does it mean there are no servers at all?\nOf course not. There are still servers behind scenes, but you don't have to worry about maintaining the servers and reserve their capacity. Your infrastructure is scaled automatically, and you just pay only for what you use.\nDoes this kind of architecture have only pros or there are some drawbacks?\nLet's leave the discussion of all the smaller pros and cons of serverless applications for another article.\nI will focus on the biggest drawback which is an impact on our code. Frameworks that we use in our daily PHP development are not ready to work with lambdas because they were not designed for those kinds of architecture.\nImagine you are a PHP developer and you want to run serverless microservice using one of the most popular frameworks like Symfony or Laravel. Imagine you can develop your microservice locally and just deploy it as lambda functions. Is it possible with PHP\nprogramming language? Yes, it is. Even if AWS Lambda does not have native support for PHP.
\nSince AWS lambda supports custom runtimes, you can create one for PHP and run your lambda functions written in that language. There are plenty of articles which describe the process of creating custom runtimes, but believe me it's time-consuming and not super easy.\nLet's take a look at the bref.sh project and try to run a simple Symfony app as lambda.
\nI assume you have knowledge about Symfony framework, or you have an existing project and some knowledge about AWS platform.
\nBefore we start please make sure you have installed:
\nFirst, we have to add Bref to our project with composer require mnapoli/bref\nThen from your project root command line run vendor/bin/bref init\nIt will create two additional files in your project template.yaml and index.php.\nYou can remove index.php for this moment, as it will be unnecessary.
As you may know, AWS lambda filesystem is read-only excluding /tmp dir\nSo we have to extend src/Kernel.php of Symfony with these two functions
public function getLogDir(): string\n {\n // When on the lambda only /tmp is writeable\n if (getenv('LAMBDA_TASK_ROOT') !== false) {\n return '/tmp/log/';\n }\n\n return $this->getProjectDir().'/var/log';\n }\n\n public function getCacheDir(): string\n {\n // When on the lambda only /tmp is writeable\n if (getenv('LAMBDA_TASK_ROOT') !== false) {\n return '/tmp/cache/'.$this->environment;\n }\n\n return $this->getProjectDir().'/var/cache/'.$this->environment;\n }Let's take a closer look at template.yaml
\nResources:\n Website:\n Type: AWS::Serverless::Function\n Properties:\n FunctionName: 'symfony-website'\n CodeUri: .\n Handler: public/index.php\n Timeout: 30 # in seconds (API Gateway has a timeout of 30 seconds)\n MemorySize: 1024\n Runtime: provided\n Layers:\n - 'arn:aws:lambda:us-east-1:209497400698:layer:php-73-fpm:1'\n Events:\n HttpRoot:\n Type: Api\n Properties:\n Path: /\n Method: ANY\n HttpSubPaths:\n Type: Api\n Properties:\n Path: /{proxy+}\n Method: ANY\n\n Console:\n Type: AWS::Serverless::Function\n Properties:\n FunctionName: 'symfony-console'\n CodeUri: .\n Handler: bin/console\n Timeout: 120 # in seconds\n Runtime: provided\n Layers:\n - 'arn:aws:lambda:us-east-1:209497400698:layer:php-73:1' # PHP\n - 'arn:aws:lambda:us-east-1:209497400698:layer:console:1' # The \"console\" layerThanks to the configuration stored in template.yaml, Bref will create CloudFormation with two most important resources which are lambda functions that will handle all the requests. One called symfony-website and the second symfony-console, both names are defined under FunctionName key.\nTheir execution will be available thanks to API Gateway which also will be created during the deploy process.\nFor testing purpose, you don't have to change template file much. Please remember to check your AWS default region if it's different than us-east-1 just change it in all Layers key of your Resources.
OK. Let's check how it works and deploy.\nFirst, we need to create s3 bucket per our app with simple AWS CLI command aws s3 mb s3://<bucket-name>\nThen upload the code and generate the stack configuration:
sam package \\\n --output-template-file .stack.yaml \\\n --s3-bucket <bucket-name>Finnaly deploy our microservice:
\nsam deploy \\\n --template-file .stack.yaml \\\n --capabilities CAPABILITY_IAM \\\n --stack-name <stack-name>After we receive output \"Successfully created/updated stack -
Lambda Functions:
\nAPI Gateway:
\nJust check your execution url in API Gateway:
\nOther drawbacks: But still I think this is a great starting point and I believe it can solve two major problems of the \"serverless PHP\":\n
\n\n
\nFurther info
\n\n
","fields":{"slug":"/php-serverless-with-bref/","tags":["Symfony","PHP","serverless"]}}}]}},"pageContext":{"slug":"/tags/serverless","tag":"serverless","categories":["Architecture","Coding","DevOps","Engineering","ProjectManagement","QA","Social","TechRadar"]}}