One cloud client per watched service

pires / consul-lb-gce

A smart Google Cloud Engine load-balancer manager for Consul backed services.

Apache License 2.0

10 stars 1 forks source link

One cloud client per watched service #2

Open pires opened 8 years ago

pires commented 8 years ago

We use one cloud client for all watched services. Cloud operations are blocking so this may hinder the scalability of the application. We should probably move to a cloud-client per watched service.

This enables:

Using different project IDs, one per service at least
Using different networks, one per service at least

This requires:

Using service labels as source of truth for project ID, network, etc.
Configuration multi-project support, e.g. authorization for each project

pires commented 8 years ago

Configuration multi-project support, e.g. authorization for each project

Actually, we should use one instance of this service per project. Also, it shouldn't block the current issue because all clients would use the same credentials.

However, how does GCP API behave when multiple concurrent API requests are made per project?