Proceedings of the International scientific and practical conference ―Science in the Era of Globalization‖ (May 22-24, 2026) / Publisher website: www.naukainfo.com. - Zurich, Switzerland, 2026. - 353 p.

111 from the hardware layer. The findings are intended to give an idea for developers to create their own microservice applications while relying on fewer external libraries, thereby extending the overall lifecycle of the system. The proposed communication system was developed using standard TCP layer connections and embedded libraries without the use of additional upper-layer software. Keywords: microservice; TCP/IP; communication; network; layer; application; event Most of the studies in our research [1-5] used standard application-layer libraries and methods to communicate microservices, including RestApi (Representational State Transfer Application Programming Interface), Apache Kafka (open-source distributed event streaming platform), RabbitMQ (messaging and streaming broker, which is easy to deploy on cloud environments). They are all good, but what if we want to speed up communication or what to do if those libraries would become outmoded and developers stop theirs support? To prolong lifecycle of your microservice application it is vital to take over the most common part of it – communication between microservices. Let‘s take a look at TCP/IP model‘s layers (table 1). Table 1. TCP/IP layers Layer Example (protocols) Application HTTP (hypertext transfer protocol, FTP (file transfer protocol) Transport TCP (transport control protocol), UDP (user datagram protocol) Internet ICMP (internet control message protocol) , ARP (address resolution protocol), IP (internet protocol) Link Ethernet, Fiber optic, Wi-fi The closer location of the layer to hardware the quicker communication. Thus quickest layer is link and the slowest is application. As for implementing software the easiest is in application layer and the hardest is in link layer.