title: How to handle multiple threads for laravel jobs?
body: <p>I am working on a laravel project which involves the customers of the application to import data into the application through various other APIs.</p>
  
  <p>I am thinking of making jobs for each kind of data that needs to imported. But, that would mean that many customers will be raising jobs that need to be worked by queue workers which means that if a customer has raised a job to import one job which is importing a certain kind of data, if another customer also raised a job to import the same kind of data, he would have to wait for the first customer's job to complete and then the second customer's job would be started to work by the queue working. But then we cannot have 100 customers waiting for each other.</p>
  
  <p>So what would be a viable solution for this kind of imports? Should I put the jobs on hashed queues and then call those queues? Or is there a better way to handle this. Has anyone ever worked with such an application where data was being imported from various APIs by customers asynchronously. And how to handle it best.</p>