title: MVC (Laravel) where to add logic
body: <p>Let's say whenever I do a CRUD operation or modify a relationship in a specific way I also want to do something else. E.g., whenever someone publishes a post I also want to save something to a table for analytics. Maybe not the best example but in general there's a lot of this "grouped" functionality. </p>
  
  <p>Normally I see this type of logic put into controllers. That's all fine an dandy until you want to reproduce this functionality in lots of places. When you start getting into partials, creating an API and generating dummy content it becomes an issue with keeping things DRY. </p>
  
  <p>The ways I've seen to manage this are events, repositories, libraries, and adding to models. Here are my understandings of each:</p>
  
  <p><strong>Services:</strong> This is where most people would probably put this code. My main issue with services is that sometimes it's hard to find specific functionality in them and I feel like they get forgotten about when people are focused on using Eloquent. How would I know I need to call a method <code>publishPost()</code> in a library when I can just do <code>$post-&gt;is_published = 1</code>? </p>
  
  <p>The only condition I see this working well in is if you ONLY use services (and ideally make Eloquent inaccessible somehow from controllers all together).</p>
  
  <p>Ultimately it seems like this would just create a bunch of extra unnecessary files if your requests generally follow your model structure.</p>
  
  <p><strong>Repositories:</strong> From what I understand this is basically like a service but there's an interface so you can switch between ORMs, which I don't need.</p>
  
  <p><strong>Events:</strong> I see this as the most elegant system in a sense because you know your model events are always going to be called on Eloquent methods, so you can write your controllers like you normally would. I can see these getting messy though and if anyone has examples of large projects using events for critical coupling I'd like to see it. </p>
  
  <p><strong>Models:</strong> Traditionally I'd have classes that performed CRUD and also handled critical coupling. This actually made things easy because you knew all functionality around CRUD + whatever had to be done with it was there. </p>
  
  <p>Simple, but in MVC architecture this isn't normally what I see done. In a sense though I prefer this over services since it's a bit easier to find, and there are less files to keep track of. It can get a bit disorganized though. I'd like to hear downfalls to this method and why most people don't seem to do it.</p>
  
  <p>What are the advantages / disadvantages of each method? Am I missing something?</p>