title: In DDD and CQRS, for Read queries, what is a strategy that allows for interfaces and easy testing?
body: <p>I'm using PHP/MySQL...</p>
  
  <p>I'm using interfaces for repositories on my Domain "command" side. This is going well. But I'm stuck on what to do on the "queries" (read) side. Do I make queries each as separate methods grouped in classes by some common similarity I find? Or do I make each query its own class? How should I go about using interfaces to make testing (and easier replacement later)?</p>
  
  <p>Some places I've researched:</p>
  
  <ul>
  <li><a href="https://github.com/malocher/zf2-cqrs-sample/blob/master/module/Application/src/Application/Controller/TodoController.php" rel="nofollow">A github php example</a></li>
  <li><a href="https://www.cuttingedge.it/blogs/steven/pivot/entry.php?id=92" rel="nofollow">An attempt to find the best decoupled approach to the read-side queries.</a> Examples use C# unfortunately and make it a bit more challenging to grasp.</li>
  </ul>
  
  <p>These solutions are convoluted?</p>