Skip to content

Commit 057ca05

Browse files
authored
Merge pull request #97098 from Nickomang/reliablecolupdate
Clarified use of external store
2 parents b6b2165 + e42010c commit 057ca05

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/service-fabric/service-fabric-common-questions.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,8 @@ Reliable collections are typically [partitioned](service-fabric-concepts-partiti
143143

144144
- Create a service that queries all partitions of another service to pull in the required data.
145145
- Create a service that can receive data from all partitions of another service.
146-
- Periodically push data from each service to an external store. This approach is only appropriate if the queries you're performing are not part of your core business logic.
146+
- Periodically push data from each service to an external store. This approach is only appropriate if the queries you're performing are not part of your core business logic, as the external store's data will be stale.
147+
- Alternatively, store data that must support querying across all records directly in a data store rather than in a reliable collection. This eliminates the issue with stale data, but doesn't allow the advantages of reliable collections to be leveraged.
147148

148149

149150
### What's the best way to query data across my actors?

0 commit comments

Comments
 (0)