Hi Santanu,
I'm not sure I know enough about your requirements to advise.
In microservices for each piece of data I'd have only one of the
services be the "source of truth" for that data and others subscribe to
events from that microservice.
In your original case, however, it's not clear if
Hi Michal
I mean eventual consistency only.
Another use case for such data consistency is for Microservices.
While each microservice will have its own data - certain entities are
required to be in synch across services.
Can consistency (eventual, of course) can be maintained by having
Hi Santanu,
If data consistency is key, please start by thinking carefully about
what you mean by consistency. How strong your consistency guarantees
actually need to be?
I see no reason not to build your system using akka, but be aware that
message-driven distributed systems will generally
*Please suggest if Akka can be used for the following use case:*
I have to run an application for two different user groups one from the
Intranet and another from the Internet.
The company policy requires me to run this applications from two different
hosting sites
Each site would contain
