Roland Kuhn

If the actor decides that the event log is corrupted and that it cannot continue, then it can and should terminate with a failure. In this case, the failure will...

There wouldn’t be any difference to just throwing instead of returning Impossible, right? Throwing an exception is pure as long as it leads to process termination, which is the case...

This is not immediately necessary, the cost with the current approach is that many threads (hundreds) are needed for the AWS client library but it works well enough.

Ignoring tags would be easy but anything more complicated is currently out of scope. There is an existing ticket for documenting constructor arguments (#4).

Yes, this is an open issue and I have currently no time to work on it—if you have an idea please share.

This is a current limitation: scaladoc comments are not parsed and interpreted , only minimal substitutions are made. This means that `[[...]]` syntax can only be used to link to...

The BatchActor will have to keep track of the size of each write batch and then only request that number of new elements when the database result comes back.

Thomas Gleixner’s implementation indeed looks interesting; the described main use-case also exactly matches what Akka needs—we have been more or less happy with our own Netty rip-off :-) but a...

I concur: a WebSocket is established by connecting to an URL, which always includes a path (that may just be `/` but very often isn’t). The point of WS is...

How about a hybrid approach regarding the event type: have the user spell out the precise enum they want to use (which is not much work and provides occasion for...