We based our project on the akka-http-rest example you linked, and it's been working pretty well for us. We aren't super far along yet, and we switched out the backend for Couchbase, but so far so good.
I like having routes, services (controller?) and backend (data) layers, it seems to be providing good separation of concerns so far. Jason On Thursday, August 27, 2015 at 3:26:48 AM UTC-7, Halvor G. Bjørnstad wrote: > > Hey. > > We're a new team planning to convert our backend services to akka-http > projects, but we're unsure on the conventional structure of said projects. > > The activator templates we've found consist of a Main class and numerous > traits implemented in one big hierarchy[0]. > Other examples include net-a-porter's somewhat older case study[1] which > implements the application logic with an actor system. > > What is the recommended approach? We're leaning more towards traits than > explicit actor systems at the moment, as we'd avoid some of the excessive > plumbing required to get the actor system running. > > Thanks for your time, > Halvor Granskogen Bjørnstad. > > > [0]:https://github.com/ArchDev/akka-http-rest#master > [1]: > http://techblog.net-a-porter.com/2013/12/ask-tell-and-per-request-actors/ > -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
