title: Is Azure Service Fabric Stateful Service State shared across partitions?
body: <p>I'm working on a Stateful Service that manages inventory for a bunch of products for our customers. Each customer belongs to a tenant group which may have an instance of this stateful service in his own partition. So a tenant with Id 10 and a tenant with Id 11 may be in a same partition (let's assume).</p>
  
  <p>Each tenant has access to Inventory for an Item with Id = 100 (for example). Each time a person wants to purchase this item, I check if the Inventory exists for this tenant, if not, I notify the calling application (a Reliable Actor in this case) and let him know.</p>
  
  <p>However, I've noticed that I was storing a reliable dictionary with the Key of the Item Id and the inventory counts. I noticed that even though the services belong to separate partitions, they still accessed the same object. Is this true that even though these services reside under different partitions, that they still have the same underlying state? </p>
  
  <p>If so, would it make more sense to store this information directly at the Actor level? I didn't see reliable collections at the actor level and thus I built a Stateful Service that would be invoked by an Actor but in my prior Akka implementations, I would store this state at the Actor level.</p>
  
  <p>I'm curious if anyone has implemented something similar and could shed light on this.</p>
  
  <p>Thank You in advance for your responses!</p>
  
  <p>Anup Marwadi</p>