Services/MessageQueuing: Difference between revisions

Services/MessageQueuing (view source)

24 bytes removed , 3 November 2011

m

no edit summary

Confirmed users

192

edits

@@ Line 77: / Line 77: @@
 . The message may be deleted after it has been sent. The only problem in
-   this case is that there is still no guarantee it has been processed, and
+this case is that there is still no guarantee it has been processed, and
-   acquiring a lock to consume a message, and the resulting write-back to
+acquiring a lock to consume a message, and the resulting write-back to
-   delete it is expensive.
+delete it is expensive.
 . One consumer per queue/partition. This requires some guess-work up-front
-   about how many consumers will be around. Since consumers can consume from
+about how many consumers will be around. Since consumers can consume from
-   multiple queue/partition's at once, there needs to be at least as many
+multiple queue/partition's at once, there needs to be at least as many
-   partitions for a queue, as desired consumers. The advantage with this
+partitions for a queue, as desired consumers. The advantage with this
-   approach is that locking is only necessary when adding/removing consumers
+approach is that locking is only necessary when adding/removing consumers
-   to ensure one consumer per partition.
+to ensure one consumer per partition.
 This MessageQueue project goes with the second option, and only incurs the