Service Discovery in the gateway service List and ELB could solve the problem?

[sbilello]

Hello!

I was wondering if placing an ELB for each service https://github.com/pipedrive/graphql-schema-registry/blob/master/examples/gateway_service/remote-data-source.js#L17 would be a workaround to deal with the service discovery.
I can imagine that each endpoint instead to be an actual server is a load balancer so we would not need to update the service list frequently.
Would it make sense or it should be more complicated with some consul discovery mechanism in place?

Thanks

[tot-ra]

Hey. I guess its up to you to decide how you discover & route traffic here. If its ELB, or you discover IPs dynamically somehow every time, or you use DNS resolution. We use consul for service discovery so example was intentionally simplified

[sbilello]

Regarding the consul approach: Is the apollo/gateway responsible to query the consul API endpoint to fetch the graphql services every 5 sec in polling fashion?

[tot-ra]

@sbilello we're resorting to querying and caching it for ~10-20s. So its kinda like polling, if there is constant load yes.