How to properly track the life of a microservice?

Question

Service Oriented Architecture

Good day gentlemen and ladies!

I am new to microservices and so I apologize in advance for my ignorance.
As I understand it, a microservice is an application that is responsible for one of the business tasks. I am developing several microservices in php. I also have two nginx and php-fpm containers to run my php application. It turns out that one microservice requires several processes, but when I started to implement a registry of microservices , a problem arose.

When conditionally microservice_1 makes a request to the registry "I'm alive buddy!", the registry writes the ip of the php-fpm container, not nginx. Therefore, in the registry, we see the ip not of the nginx microservice, but of itsphp-fpm . There was an idea to shove both php-fpm and nginx into one container, which is bad practice.

Question How to make the microservice specify the ip of its nginx, not php-fpm, when registering? Because the entry point is nginx. Or perhaps there are other ways to implement a microservices registry in docker.

Thank you !

Answer 1

Discover, Register and Resolve services for application...