Thank you. I totally understand that. And I guess my question has been answered between lines as well. So I will stand down.
Just an/my opinion, but it may have been more beneficial for Akka developers to get that kind of "magic" (framework) as an extended layer of the agents model. E.g. having the Service construct as a special node in the actors system hierarchy. With a dedicated purposed interface/impl. Most projects I guess will not rely on "pure" microservice architecture and may have polyglot persistence as well. Injecting these ideas as an organic layer in Akka may have had its own benefit. I stand down. I appreciate the help. And will likely adopt Akka on its own without the upcoming Lagom Scala APIs. Thank you. On Sunday, July 3, 2016 at 3:32:39 PM UTC-4, Christopher Hunt wrote: > > Akka is a low level toolkit. Lagom is a higher level framework. Frameworks > are opinionated and tend to be strongly focused on developer productivity. > This is a goal of Lagom. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
