Reference Architecture for Microservices with an Optimized Inter-Service Communication Strategy

In the modern world, most software developers follow the microservice architecture for their software development. As a result, monolithic architecture-based software is also gradually transforming toward new microservice architecture. The main reason for using microservice architecture is to achieve the main software quality attributes such as scalability, maintainability, performance, portability, modifiability, and testability. Architects should consider product development and product deployment to achieve those quality attributes. Microservices must communicate with each other to produce reliable output, act as an independent service, and be deployed in distributed environments. The primary challenge in microservices architecture lies in software performance degradation, specifically in terms of response time and throughput, due to inter-service communication over the network. This research mainly focuses on the reference architecture for microservices to mitigate the challenges, which uses a request response-based steam TCP communication strategy for inter-service communication in both on-premise and cloud-native environments. People can achieve better performance and meet the main quality attributes with the suggested reference architecture.