LibraryToggle FramesPrintFeedback

The claim check pattern, shown in Figure 8.4, allows you to replace message content with a claim check (a unique key), which can be used to retrieve the message content at a later time. The message content is stored temporarily in a persistent store like a database or file system. This pattern is very useful when message content is very large (thus it would be expensive to send around) and not all components require all information.

It can also be useful in situations where you cannot trust the information with an outside party; in this case, you can use the Claim Check to hide the sensitive portions of data.


The example route is just a Pipeline. In a real application, you would substitute some other steps for the mock:testCheckpoint endpoint.

Comments powered by Disqus
loading table of contents...