How Do Your Decision Microservices Communicate?

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.

This entry was posted in Architecture, Microservices. Bookmark the permalink.

1 Response to How Do Your Decision Microservices Communicate?

  1. jacobfeldman says:

    Consider to use “AWS Step Functions”
    “Step Functions is a serverless orchestration service that lets you easily coordinate multiple AWS Lambda functions into flexible workflows that are easy to debug and easy to change. Step Functions will keep your Lambda functions free of additional logic by triggering and tracking each step of your application for you.”

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s