bref VS serverless-application-model

I have just released the first working version of a symfony starter project using bref.sh.

As you can see on the website (https://bref.sh/) there's 13 billion monthly AWS Lambda invocations using Bref (PHP).

I have a PHP application (running on Amazon Linux via Bref on Lambda) which has been signing Apple passbooks no problem. I've trying to do various upgrades which includes moving to AWS Linux 2023 which uses OpenSSL 3.

Your best bet is to post an issue on https://github.com/brefphp/bref

multi threading php isnt a burden. laravel with a supervisor + redis + queues works out-of-the-box. you can even run it on lambda (vapor or bref.sh) with almost no hassle.

To generate resource on AWS, you can use aws-sdk into a lambda. While Node or Python is more widely used, you can use PHP bref.sh and the PHP AWS SDK to achieve the same outcome. You'll want to use serverless framework (https://www.serverless.com) .

If you’re deploying in AWS and depending on your app I’d highly recommend using https://bref.sh/. When we changed it made our deploy pipeline so much simpler and our AWS bill much cheaper. Plus infrastructure as code is so useful (we don’t have dedicated dev ops in a team of about 20). Things like adding GD, upgrading PHP, or even adding a redis server become 1 (or a few) lines of change which you can PR and test on staging just like other code changes.

For Lambda, look into https://bref.sh/. For us, running on Lambda was always way cheaper than everything else. However, if you have massive scale that calculation may not hold up.

There's a lot to unpack here from your question. First off, PHP on Lambda WITHOUT docker is possible. Check out https://bref.sh. It works by providing PHP on Lambda like any other runtime. It also provides a Web Hosting experience for PHP on Lambda for those that want to run PHP-FPM.

Failing that, looks like Bref will be the option in place of Vapor.

The complete solution with SAM is available here.

There are many options to deploy Serverless Applications in AWS and one of them is SAM, the Serverless Application Model. I chose to use it here, because it doesn't add too many layers of abstraction between what's being deployed and the code we write and our infrastructure is quite simple.

The solution uses AWS SAM with the global configuration for Lambda functions and the public API you can use to access Apache Zeppelin. The stack deployment provides the URL as an output value.

When you combine this with the AWS Serverless Application Model you can also very easily include your dependencies. Or use a compiled language like golang for your Lambda functions. You simply run sam build before you run the aws cloudformation package and aws cloudformation deploy commands. SAM will build the binary and update the template to point to the newly built binary. Package will then upload it to S3 and replace the local reference to the S3 location. Deploy can then create or update the stack or you can use the CloudFormation integration in CodePipeline.

I'm a big fan of using an Infrastructure as Code (IaC) approach for any project. My go to tools for this are the Servlerless Application Model (SAM) and it's associated CLI (SAM CLI). For more official use cases and for cross platform apps I typically use Terraform.

AWS SAM

Kicking off the tour and not starting a war, but I'm going to be using the Serverless Application Model.

The diagram here is super simple. I'm going to write something a little later that shows how this code could fit into a bigger workflow, but for now, I'm keeping it basic. And yes, that's the SAM Squirrel in there.

Interestingly, AWS CDK and SAM are both explicitly mentioned. While CDK broadly addresses Infrastructure as Code, SAM is highlighted for its role in developing serverless data pipelines - a hugely underrated concept.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.