title: Where to put business logic when you don't have a specified model for that feature? Laravel
body: <p>I'm trying to improve my code OOP wise.
  I have the tendancy to put some of my bussiness logic inside my Controller.</p>
  
  <p>Some people told me this is not desirable.</p>
  
  <p>I know that when you are working with Posts for example. You can simply put your bussiness logic in your <code>Post.php</code> Model.</p>
  
  <p>I now have a feature where i upload an .xlsx file and it has to be checked and validated if the format of the .xlsx is correct. </p>
  
  <p>It is currently inside <code>ScheduleController@storeDeliveryXlsx</code>. </p>
  
  <p>But i don't have a specified model for this to store the validation inside? </p>
  
  <p>Is this where Repositories design pattern is needed? Or is it fine to create a model that doesn't communicate with the database like: <code>DeliveryFile.php</code> where i put the logic that i later can use throughout my app like this: <code>DeliveryFile::validate($file);</code> or <code>DeliveryFile::upload(file);</code>.</p>
  
  <p>I think i'm likely to re-use the same validation on the .xlsx for multiple instances. So i'd like to do something like <code>Model::validate($file);</code>. But i don't know where to put the code.</p>