trying to understand why I should use this over Laravel's built-in scheduler

[vesper8]

Hi there,

First of all please understand I am not trying to undermine your package here which is obviously very appreciated by a lot of people.

I used to use my own job scheduler way back when I was using a legacy framework, I switch to Laravel about a year ago and am at the point where I am working on a project which needs to create a lot of jobs which will then be queued to beanstalk at specific times.

It seems that I could do all this using the built-in scheduler but I also see that using your tool would allow for some built-in monitoring and the use of tables to better track what's going on.

On the other hand I need my jobs to run only once and I need to be able to add them dynamically and it seems like there's no easy way to do that with your package. Add them dynamically yes there's a few examples.

Also I figure that if the cron does nothing more than queue up something in beanstalk then it won't benefit from the job monitoring since it won't know if it fails as queuing up the job itself will always succeed.

So I see some pros and cons but mostly just wondering if this was very popular in the days before Laravel 5's pretty nifty built-in scheduling which also handles cron commands and today it's lost some its appeal? No disrespect meant whatsoever just trying to decide if I want to use it.

Thanks if you respond!

[liebig]

Hi,

Cron was developed when there was no job scheduling for Laravel. With Laravel 5 there are basic scheduling functionalities and under the hood we are using the same PHP libraries such as cron-expression. But Cron delivers some additional functions like the monitoring, the in time check or the integrated route. If you don't need this features, I wouldn't use Cron. By using external dependencies, your application dependent on the support of developers like me. I make mistakes (like bugs) and maybe sometime I won't support Cron anymore. And using external dependencies expands your application. And if the functionality is already build in Laravel, I would use this.

I hope this helps.

[liebig]

Closed due to inactivity.