Our great sponsors
fl-aws | bref | |
---|---|---|
1 | 41 | |
15 | 2,983 | |
- | 0.9% | |
0.0 | 9.4 | |
over 7 years ago | 12 days ago | |
PHP | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fl-aws
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
Living in my team's bubble i thought everyone runs or tries to run parallel environments: prod, staging, dev, but also an individual (person) or feature env. Why? Because there's no emulator or documentation that will teach you real behavior. Like others have said, AWS seems out of this world. Just like GCP and Azure i might add. Some things you don't expect and they mesmerize you how smart they are. Some you expect and you can't fathom how come you're the "only" one screaming. Random thought: this is how i ended up logging all I bumped into into "Fl-aws" https://github.com/andreineculau/fl-aws
Back to the point: reality is that many build their AWS environment (prod) manually, maybe they duplicate once (dev) also manually, maybe they use some automation for their "code" (lambda) but that's it. This implies it's practically impossible to run end-to-end tests. You can't do that in prod for obvious reasons and you can't do it in dev either - you have many devs queueing, maybe dev is not in sync with prod etc.
My team ran cloudformation end-to-end. We actually orchestrated and wrapped cloudformation (this is yet another topic for not using terraform etc) so that if smth couldn't be done in CFN, it would still be automated and reproducible. Long story short, in 30 minutes (it was this long because we had to wait for cloudfront etc) we had a new environment, ready to play with. A total sandbox. Every dev had their own and it was easy to deploy from a release artifact or a git branch to this environment. Similarly you could create a separate env for more elaborate changes to the architecture. And test in a live environment.
Finally to your question: how do you test end-to-end?
If we talk about lambdas because that's where the business logic lies in a "serverless" architecture, then the answer is by calling the system which will eventually call your lambda/s along the way. If your lambda ia sitting behind AWS gateway, then fire an http request. Is it triggered when objects land on S3? Then push some object to S3. How do you assert? Just the same - http response, S3 changes etc. Not to mention you can also check cloudwatch for specific log entries (though they are not instant).
With this type of a setup, which sounds complex, but it is not since it is 100% reproducible (also from project to project - I had several), adding this proxy-to-my-dev-machine lambda would mean I can make local changes and then fire unit AND end-to-end tests without any changes pushed to AWS, which is the main time/energy consumer imo.
PS: sorry for the wall of text. Like i said i recently realized that the development realities have huge discrepancies, so i tried to summarize my reality :)
bref
-
Serverless Symfony Starter - Deploy Symfony to AWS
I have just released the first working version of a symfony starter project using bref.sh.
-
A bank runs serverless with PHP and AWS Lambda
As you can see on the website (https://bref.sh/) there's 13 billion monthly AWS Lambda invocations using Bref (PHP).
-
Configuring OpenSSL 3 to sign an Apple Passbook?
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.
-
Bref + SQS - Runtime.unknown
Your best bet is to post an issue on https://github.com/brefphp/bref
-
Software architecture applied to PHP
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.
-
Project advice
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) .
-
Ideas for minimum PHP pipeline for a small team
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.
-
Is fargate the right choice for my apps?
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.
-
Datadog on AWS Lambda for PHP with Bref
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.
-
Laravel Vapor, security information?
Failing that, looks like Bref will be the option in place of Vapor.
What are some alternatives?
aws-lambda-runtime-interface-emulator
lambda-debug-proxy - A proxy for piping AWS lambda input payload+context to and returning a response from a local dev environment for debugging.
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
Laravel - The Laravel Framework.
Lumen - The Laravel Lumen Framework.
PHP-DI - The dependency injection container for humans
octane - Supercharge your Laravel application's performance.
sidecar - Deploy and execute AWS Lambda functions from your Laravel application.
laravel-bridge - Package to use Laravel on AWS Lambda with Bref
sst - Build modern full-stack applications on AWS
Doctrine Migrations - Doctrine Database Migrations Library