|
|
|
|
|
by upupandup
1421 days ago
|
|
The problem I find with these plugin serverless is that they rarely work well. Even with a framework produced by Chalice, there are issues that are largely so minor in detail but required to work well with AWS. Often they are not even code related but infrastructure. IMHO, AWS Chalice remains the goto method to generate REST API serverless manner but also curious how yours also differ from the paid Laravel solution that lets you deploy your stack serverless. |
|
Sidecar (my library) provides no REST API. You just... call the function from PHP. So you'd call it like
And that would run the function _on Lambda._ Whether that function is JS, Ruby, Python, whatever.With Sidecar, you never have to configure anything in the AWS console, besides the initial IAM configuration. You give Sidecar admin keys, it configures all the permissions, roles, etc, and then self-destructs the admin keys. So you don't have to muck around with anything at all.
> also curious how yours also differ from the paid Laravel solution that lets you deploy your stack serverless.
Sidecar deploys and executes _non-PHP_ functions from your Laravel app. So it's completely different. Vapor deploys your whole app and runs it on Lambda, I just deploy single functions at a time.