Read this if you haven't
https://doc.akka.io/docs/akka/2.5/scala/dispatchers.html#blocking-needs-careful-management
You can start with a single Actor for JMS and one for file IO, each
configured with a custom dispatcher.
Or use Futures, with custom dispatchers provided as ExecutionContext.
On
Hi,
I have been learning Akka Streams lately in a bid to use it to build a
utility to handle a batch scenario I have.
I have been looking also at Akka Http also but have become a bit blocked
because although the documentation is quite extensive there are not many
examples.
My use case is
Hi,
We are doing a lot of blocking operations: file reading + synchronous JMS
sending. (Currently not really possible to make use of the async
alternatives)
Events come in: for each event, 1-x files are read and parsed until an
end-event comes in, meanwhile the results are sent to an
