title: How fine-grained can Actors be?
body: <p>This is a beginner Akka question (And maybe I am seeing Actors everywhere) </p>
  
  <p>I have an sql table "books". (5 million rows) The queries I want to run need to be as fast as possible. The where clauses are quite complex. And I want the queries to run under a sec. That is why I need a pure memory solution</p>
  
  <p>Does it make sense to have an actor for each book row?</p>
  
  <p>With this design I would have a "bookManagerActor" which would manage its 5 million child "bookActors"</p>
  
  <p>The "bookMangerActor" should reply to messages like "filter books of date" or "sort books by date and name" (the sorting and filtering could take some time and the filters can be composed)</p>
  
  <p>Or should I just use a java.util.Set in my bookManagerActor?
  Do I get any benefits from modelling single books as Actors?</p>