Hi,
I am new to akka streams, and working on a project having both real-time
and batch needs. In the batch cases, I need to take context (e.g.,
requestID), from the initial request, and apply it at the end of batch-item
processing. The batch-item subflow is by itself rather simple: (parse,
Hello
We're implementing microservice system consisting of several services
representing completely different domains.
Let's consider that we have following
- wallet service representing customer balance, supporting deposit,
withdraw and get balance commands
- wallet client service
Thanks Rafał
Already figured it out :)
понеділок, 8 травня 2017 р. 17:58:51 UTC+3 користувач Rafał Krzewski
написав:
>
> Hi Evgeny,
>
> In such situation I'd
> use de.heikoseeberger.constructr.coordination.Coordination (it's subclass
> specific for the data store you are using) on the nodes
Im finding the idea of Akka Stream a very nice fit to the application im
building. Im building a realtime decision system with the following
functionality.
1. Make HTTPS POST request to get a *sessionToken* string
2. Start a keep-alive service to ping session server at 3h intervals
3.
The hosting within an Actor is a perfectly fine and valid solution IMHO.
On Tue, May 9, 2017 at 4:04 PM, 'Michal Borowiecki' via Akka User List <
akka-user@googlegroups.com> wrote:
> Sounds like what could help in your organization is using a higher-level
> abstraction, such as Lagom.
>
> You
Sounds like what could help in your organization is using a higher-level
abstraction, such as Lagom.
You don't need to be comfortable with actors to use it and it does
provide a wrapper around reactive-kafka (or akka-stream-kafka as it's
currently known) with exponential backoff restarts:
