Hi everyone, i'm running an akka based backend that will potentially be used by 
20k-200k daily users. I am specifically using cluster sharding but without 
using persistence actor, only regular actors whose state is being recovered on 
preRestart. The actor is abstracting orders with unique id, the shard resolver 
basically is getting these id, mod it by 100 to generate its shard lication. I 
looked into the journal and i saw that on the column persistence id, only one 
persistence id is listed, and that was /shardcoordinator/order, and an 
increasing sequence number.

As i understand it, the persistence id on the journal should represent a 
specific persistent actor. My questions are:
1. Will the approach causes problem in the long run?
2. I saw that the sequence number is increasing, will that means that in the 
long run creating an entry actor takes a longer time?

Im using akka persistence 2.4 RC3.

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