A.) Have a shared database that allows both applications to read and write to the tables to share the data instead of having to communicate<\/p>\n
B.) Use asynchronous messaging to send and receive messages between each microservice<\/p>\n
C.) Abandon the microservice architecture so no interaction is needed<\/p>\n
D.) Create a third service to handle the interaction between the services<\/p>\n
E.) Use a RESTful architecture for both, send the ID through a POST, and ping the service with a GET until a response is available<\/p>\n
Answer:-\u00a0<\/strong>A.) Have a shared database that allows both applications to read and write to the tables to share the data instead of having to communicate<\/p>\n In asynchronous communication microservices implement asynchronous messages or http polling<\/strong> to connect with other microservices, but the customer request is served right away. Whenever we produce a pod in Kubernetes, this mechanically allocates an internal IP to it. The IP will be picked up from CIDR range and will be assigned to the Pod. This IP will be available throughout the cluster and using this IP any pod can address our web-server.<\/p>\n","protected":false},"excerpt":{"rendered":" A.) Have a shared database that allows both applications to read and write to the tables to share the data instead of having to communicate […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"yoast_head":"\n