Having just seen this message for the first time, my feedback would be that
it's not at all clear what the message pertains to. I'm curious whether
anyone's thought there might be some use in attaching reference codes to
certain log messages so that it's easy to get context.
On Friday, December
I'm not exactly sure what you mean by an orchestration layer (I've heard a
lot of different schemes called this), especially one that receives events,
because that makes it sound stateful. But Akka HTTP makes a totally
reasonable external API layer, especially for services, as opposed to
rendering
I'm new to this space, but yes, it seems to me like the read store should
store lastProcessEventNr someplace, ideally updated in the same transaction
that updates the view.
On Friday, December 4, 2015 at 1:19:09 PM UTC-8, Adam Dohnal wrote:
>
> Hello,
>
> now I better understand queries like all
Crazy question, but I can't find the source repository online anywhere. It
doesn't appear to be in https://github.com/akka/akka/ when I search for
class names I know. "akka http repository", "akka http github", etc. don't
turn up results in Google. The website and docs also don't appear to link
