title: Do we have Akka/Scala equivalents for the OTP behaviors?
body: <p>I'm currently estimating a new project which is related to message routing and logging. I found OTP's abstractions like <a href="http://www.erlang.org/documentation/doc-4.8.2/doc/design_principles/events.html#5" rel="noreferrer">event</a> and <a href="http://www.erlang.org/documentation/doc-4.8.2/doc/design_principles/gen_server.html#4" rel="noreferrer">server</a> pretty useful for it. But due to non-technical reasons this project probably will be implemented on JVM, so I've looked at <a href="http://akka.io/docs/akka/1.2/" rel="noreferrer">Akka</a>. And haven't found anything similar.</p>
  
  <p>There is 2 reasons why I want to find something similar to generic behaviors in Akka:</p>
  
  <ol>
  <li>I'm not an expert in building distributed systems and like to have kind of best practices embedded into my tools.</li>
  <li>All Akka's stuff like <a href="http://vasilrem.com/blog/software-development/even-simpler-scalability-with-akka-through-registryactor/" rel="noreferrer">remote references and registries</a> seems a bit complicated for a simple "pass from one point to another" app. It would be great if I will be able to address components of my system by simple name right "out of the box".</li>
  </ol>
  
  <p>Am I missing something or in Akka it is a common practice to implement this kind of functionality by yourself?</p>