I have heard a lot of good things about Akka.
I have a stream of price , and I need to create two moving average of the
price.
And finally I have a strategy that listens to these price, moving average
price 1 and moving average price 2 and makes some decisions.
å
I implemented this via
I am trying to create an Akka-HTTP streaming service that supports both
JSON and protobuf.
I am able to support both formats without streaming using
Marshaller.oneOf(...) composition. However, I cannot seem to find something
similar for EntityStreamingSupport.
Would anyone have pointers on how
On Sat, Nov 26, 2016 at 10:20 AM, Patrik Nordwall wrote:
> Seems to be a lot of complexity and moving parts compared to running all
> together with same entity type.
Yeah, this is what I keep coming back to. The architecture sounds like it
could work, but I'm still
Ok, it should work.
Each entity type (customer) will have its own sharding coordinator and
manage itself independent of other entity types. If you start to have many
such (>100) I can imagine that there will be some peak loads when fail over
of the coordinator node and such, but I have not tried.
Terminated actors are automatically unsubscribed from event bus.
/Patrik
tors 17 nov. 2016 kl. 09:17 skrev Jithin Thomas :
> Hi all,
>
> I'm fairly new to Akka. So, please let me know if this question has been
> answered elsewhere.
>
> I'm building a web server application
Hi there,
3 styles answers to the question :-)
*Short version:*
Don't do it. Blocking the default dispatcher is a very very very bad thing,
do it on a dedicated dispatcher.
*Documentation version: *
First, this is very well documented here: