Key points are not available for this paper at this time.
The purpose of the study is to perform critical analysis on Inter-Process Communication (IPC) in the Microservice Architecture and to evaluate its impact on the basis of various non-business-related functionalities, such as effectiveness of performance, accessibility, adaptability, and complexity. There are various techniques for establishing IPC within Microservices, each with its own set of benefits and drawbacks. Throughout this research, IPC approaches are divided into two categories: synchronous and asynchronous. The Representational State Transfer Application Programming Interface (REST API) and google Remote Procedure Call (gRPC) are utilized in the synchronous kind, whereas Rabbit Message Queue (RabbitMQ) is utilized in the asynchronous type. A workload test was conducted across each model to get quantitative measurements on the Performance Efficiency and Accessibility of each technique, and a relatively similar functionality set was utilized to provide qualitative data on almost every other IPC method's adaptability and complexity. The research outcome shows if there is any standardized IPC solution that can be utilized in all scenarios.
Shehzadi et al. (Tue,) studied this question.