What is the purpose of this repository? about laravel-bridge HOT 4 CLOSED

Thanks, yes this directory is exactly what I started doing initially, but went back to using the native SQS integration.

Also, the way Vapor handles queues is very specific and not aligned with how the SQS + Lambda integration works. In short, they adapted Lambda to Laravel. I am adapting Laravel to Lambda. That lets us use all the features of SQS and Lambda.

from laravel-bridge.

Sorry @deleugpn, I'm a year late 😄

Since we don't need the lambda() function anymore, I don't think the facade makes sense anymore.

Regarding queues, I've always wanted to integrate with the native behavior of SQS + Lambda (i.e. not polling messages). I have finally managed to push something. If you have any chance to try that out, or review it, I would love that.

I am also looking for people with Laravel experience to tell me how to make that integration in the Laravel style (i.e. something that looks like Laravel practices). That could be with the naming, with the documentation, etc.

from laravel-bridge.

Thanks for putting this out there. Excited to see it released.

If you haven't already, take a look at how Laravel Vapor is handling it's SQS queues, tied into the Laravel systems:
https://github.com/laravel/vapor-core/tree/2.0/src/Queue

from laravel-bridge.

Closing for now, still working on this package with a proper documentation.

from laravel-bridge.