Hi Prakhyat,
I'd use persistent actors with cluster sharding.
You can start the the ClusterSharding system for different typenames that
reflect a bounded context - or - a single aggregate root (in our situation)
like:
ClusterSharding(system).start(
typeName = AggregateRootNameHere
And have these used between the bounded contexts by sending the
AggregateRootName actors messages.
One practical point for this approach: Currently you have to start your
shard types all within the same JVM (at least for your leading node)
otherwise the shardcoordinator gets issues. (I am currently changing the
BlogApp sample in order to show this behaviour, but many things todo.. so
that takes some time0
Kind regards,
Olger
On Thursday, September 25, 2014 8:17:09 AM UTC+2, Prakhyat Mallikarjun
wrote:
>
> Team,
>
> We are building app on the approach DDD/CQRS/Event Sourcing.
>
> Did you anytime have a look at this challenge
> http://abdullin.com/post/dddcqrs-challenge-integrating-distributed-systems/
> ?
>
> What are your thoughts and solutions? We are facing similar problem of
> communicating across bounded context's, looking forward for insights wrt
> *Integrating
> Distributed Systems composed of a different bounded contexts and
> applications?*
>
> -Prakhyat M M
>
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
