## Chapter 4. Message Cursors

FUSE Message Broker uses message cursors to improve the scalability of the persistent message store. By default, a hybrid approach that uses an in memory dispatch queue for fast consumers and message cursors for slower consumers is used. FUSE Message Broker also supports two alternative cursor implementations. The type of cursor can be configured on a per-destination basis.

Message cursors provide a means for optimizing a persistent message store. They allow the persistent store to maintain a pointer to the next batch of messages to pull from the persistent message store. FUSE Message Broker has three types of cursors that can be used depending on the needs of your application:

- Store-based cursors are the default cursor implementation. They offer the best all around performance.

- VM cursors are very fast, but cannot handle slow message consumers.

- File-based cursors are useful when the message store is slow and message consumers are relatively fast.