Im running two servers, one L5 with beanstalkd and one Lumen server. Lumen sucessfuly queues a job onto L5 however any data passed to the constructor of the Lumen Job class does not get transfered to L5 server.
Any ideas?
You should not consider that that Lumen and Laravel know each other. Those are 2 different frameworks and can potentially evolve in totally different ways.
The best way to decouple both is to to follow the following rule: you queue it, you run it
When you want to delegate a job to another instance/environment/microservice, create an api endpoint on that microservice that will accept the job and queue it.
That way, you will never have surprises regarding the execution of the jobs.
Thank you for your advice Ray. Would you say CURLing from Lumen to a L5 route, as a notification/ping action , and thus queuing and runing a job from L5 itself would be a good scenario?
Depends on your needs. I run a data retrieval from a big data database on a schedule like end of day reports that blogged down my laravel app.
I used lumen to run those scheduled data transfers and manipulate the data before saving to the laravel's database. No more laggy app and still the same hardware.
So it can be a benefit under the right circumstance.
Please or to participate in this conversation.