worker to run Laravel console command instead of supervisor

[marayshi]

Hi

I'm trying to deploy my laravel project with bref
every things working well like Queue worker.php
I know worker.php replace the need for supervisor to execute listener "php artisan queue:work"
I'm trying to so similar function with worker for different console command to run 24/7 with multi procs
this my supervisord config file

[program:asteriskEvents]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/laravel/artisan asterisk:events
autostart=true
autorestart=true
user=asterisk
numprocs=2
redirect_stderr=true
stdout_logfile=/var/log/supervisor/asterisk_events.log
stopwaitsecs=3600

this work as lister for Asterisk server events that come with AMI
I need a way to make this working with aws function exactly like how you do this with Queues
Please advice if this possible

[mnapoli]

Hi,

To run Laravel Queues on AWS Lambda have a look at the Bref-Laravel Bridge: https://github.com/brefphp/laravel-bridge#laravel-queues-with-sqs

[marayshi]

I'm trying to connect to Asterisk server and listening for Asterisk calls that come by sockets
I doing this by create my sockets code as laravel console command
and run supervisor service that executing this command
it should keep listening events that come any time from asterisk
and this working good within Ec2
I think no way to do this as lambda function

But what make me asking this question, that we do the laravel queues in same way with supervisor
and now it working with lambda in perfect way, but things different with queues that we know when to dispatch the queue, but with my case i dont know the time when events come from asterisk, so i have to keep listening

i hope this help to understand

[matthewsuan]

AFAIK, there is no serverless socket client offering from AWS (I wish there was!).

I think another option is to use Fargate as listener then push events to SQS or SNS or Kinesis. Then have lambda process each event. Or process each event inside Fargate directly.

[marayshi]

Thank's @matthewsuan
I will look into Fargate

[mnapoli]

Yep, that doesn't sound like a good fit on Lambda to be honest.

Fargate could be an option but I'm not sure you would gain a lot compared to EC2, it might be more expensive if you run all the time.

But nothing prevents you from running the socket watcher on EC2 and push jobs in SQS, then Lambda processes SQS. That way you can have a really small script on EC2 without Laravel, and keep only Laravel in Lambda. But it's up to you.

[marayshi]

Yes you right, this not fit to Lambda
I already doing this by EC2 and it working good, I just dreamed to put all my code parts in one place "Lambda" haha
Thank's @mnapoli 👍