After you deploy your business decision models as microservices, you need to organize your inter-service communication.  Usually, your decision microservices are stateless. But what if they need to maintain some state? What if they updated values and those values got automatically propagated to other microservices via an in-memory platform? There are no database lookups, no file system writes, and no conflicts. For example, microservices tasked with running machine learning models need to maintain the state of their models and their parameter weights. This brings the important question: where are the states stored? Watch the Hazelcast’s webinar “How In-Memory Computing Enables a New Generation of Microservices.” See also “How to Make Microservices Communicate” Share your preferred communication mechanisms with the DM Community.