Hi Ashley,

My challenge to the Akka team would be to consider how someone could use 
Akka for CQRS *without* using event sourcing to persist the actors (e.g. 
their state may just be saved to an SQL database).  Note that I have 
nothing against the current PersistentActor class, it seems great.  
[Prakhyat] I agree to your point but only for 'Q' in querying. 

I expect queries to be simple. Like 
1. JPA find queries in repositories.
2. Hibernate named queries.

In ORM each domain object knows its table. The ORM tool will translate the 
Named queries and JPA queries to dialect of connected data source. The 
framework will abstract the querying logic, developers just mention which 
domain repository to use.

Correct me If I am wrong. I want solutions from akka persistence for 
complex business querying which will connect different aggregate roots and 
complex reporting and analytic's. Also making sure data duplication should 
be avoided, only state should be maintained, replication of state to 
querying side should be avoided.

-Prakhyat M M




On Monday, 1 September 2014 11:28:56 UTC+5:30, Ashley Aitken wrote:
>
>
> Thank you Markus for a very useful contribution.
>
> I too included a link to that architecture diagram in a previous post in 
> another thread.  I think the provision of an "eventbus" for CQRS to 
> integrate with other bounded contexts on the write-side and, of course, the 
> read-side is very important and something that the current Akka proposal 
> lacks.  
>
> My challenge to the Akka team would be to consider how someone could use 
> Akka for CQRS *without* using event sourcing to persist the actors (e.g. 
> their state may just be saved to an SQL database).  Note that I have 
> nothing against the current PersistentActor class, it seems great.  
>
> As I understand it though, CQRS is completely possible without event 
> sourcing aggregate state and I believe most such implementations still 
> needs some sort of reliable / persistent event store / bus for integration 
> on the write-side and updating the read models on the read-side.
>
>

-- 
>>>>>>>>>>      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.

Reply via email to