Re: [akka-user] Re: Exposing Akka actors through a REST API

2016-11-13 Thread Roland Kuhn
Ah, right, I did not understand it that way. Then we are on perfect agreement—which is how it should be :-) Regards, Roland Sent from my iPhone > On 13 Nov 2016, at 15:04, Konrad Malawski > wrote: > > I think we misunderstood each other somehow. > I understood your goal is to have "one rout

Re: [akka-user] Re: Exposing Akka actors through a REST API

2016-11-13 Thread Konrad Malawski
I think we misunderstood each other somehow. I understood your goal is to have "one route" that somehow directly routes requests to representative actors (somehow it sounded to me like you have deep hierarchies you want to expose like that). In that sense the "route" would be driven by the structu

Re: [akka-user] Re: Exposing Akka actors through a REST API

2016-11-12 Thread Roland Kuhn
I'm not sure I agree with Konrad here: what is wrong with using an HTTP route to expose an actor as service endpoint? This does not imply that the actual implementation needs to be structured accordingly, the backend is completely independent a priori. The role of the composable route snippet is

[akka-user] Re: Exposing Akka actors through a REST API

2016-11-12 Thread Alvaro Santuy
:-( Ok, so I guesss the "correct" pattern is to always use a "Service Layer" (non-Akka, so not an actor) between the actors and the REST exposition. Am I correct? On Thursday, November 10, 2016 at 4:28:10 PM UTC+1, Alvaro Santuy wrote: > > Hello everybody. > > Is there any project out there ca

Re: [akka-user] Re: Exposing Akka actors through a REST API

2016-11-11 Thread Konrad Malawski
So my question is if there is some framework or library to easily do this mapping, from the REST end-points to the corresponding ActorRefs... I've seen people do that, however I'd argue it's a terrible anti-pattern to just "expose whatever internal state you have onto the HTTP APIs". It's like po

[akka-user] Re: Exposing Akka actors through a REST API

2016-11-11 Thread Alvaro Santuy
Hi Matt. In this project we are going to use a DDD aproach using Persistent Actors to represent Aggregate Roots. So, in some way, each Actor will map to a REST resource: I don't mean that Actors were directly exposed, a supervisor could mediate fordwarding messages from the REST front-end to th

[akka-user] Re: Exposing Akka actors through a REST API

2016-11-10 Thread Matt Edge
Not quite sure what you mean when you say you don't want to "manually encode" the routes in Akka HTTP. What is it about Akka HTTP that is giving you trouble? I personally have built a couple Akka applications with a REST API sitting in front of it. Most of the time I've used http4s but I've als