Architectural Patterns

State messaging pattern

How can services remain stateless while contributing to stateful interactions?:

Problem	When services are required to maintain state information in memory between message exchanges with consumers, their scalability can be compromised, and they can become a performance bottleneck on the surrounding infrastructure.
Solution	Instead of retaining the state data in memory, its storage is temporarily delegated to messages.
Impacts	This pattern may not be suitable for all forms of state data and should the message be lost, any state information they carried may be lost as well.

 

Problem: Services are sometimes required to be involved in runtime activities that span multiple message exchanges. In these ...