Laravel 5.3 Console Commmands vs Jobs

Despite of researching in Laravel official doc, and internet in general, I see this other post, does not actually clarify what to do if you need a heavy task able to be scheduled and queued. I mean, for instance, we have a Backup task which may be launched manually, to be run in background and periodically too.

Personally I decided to have a ConsoleCommand wich, on one hand, I schedule:run from Kernel.php, and also Artisan::queue from controller.

But this seems to me as an error mixing concepts.

Must it be a Console Command so that it can be schedule, must it be a Job to be queueable ?

via Chebli Mohamed