Service Discovery for a microservice with multiple ports

#1

Post by caspereeko » Tue, Mar 21, 2017, 1:34 PM UTC

Is exposing multiple ports per service an anti-pattern?

Does it violate the single responsibility of a microservice?

How do you handle service registration and discovery for services with multiple ports?

Is IP per container with smart clients & SRV records the best way to tackle this problem?

Re: Service Discovery for a microservice with multiple ports

#2

Post by weitzj » Tue, Mar 21, 2017, 1:37 PM UTC

I got inspired by Consul and srv records. I use different names for the protocols on each port, e.g. mqtt.mosquitto... websocket.mosquitto..

Re: Service Discovery for a microservice with multiple ports

#3

Post by caspereeko » Tue, Mar 21, 2017, 1:40 PM UTC

weitzj wrote: post #2

I got inspired by Consul and srv records. I use different names for the protocols on each port, e.g. mqtt.mosquitto... websocket.mosquitto..

So all services needs to talk to consul DNS to resolve these names, right?

How would you expose for example mqtt to public internet-facing in this case?

Re: Service Discovery for a microservice with multiple ports

#4

Post by weitzj » Tue, Mar 21, 2017, 5:17 PM UTC

caspereeko wrote: post #3

weitzj wrote: post #2

I got inspired by Consul and srv records. I use different names for the protocols on each port, e.g. mqtt.mosquitto... websocket.mosquitto..

So all services needs to talk to consul DNS to resolve these names, right? How would you expose for example mqtt to public internet-facing in this case?

I use TLS and SNi and have a public hostname for each port