Re:Kubernetes Production Patterns and Anti-Patterns
by treffer on Saturday June 10, 2017 @03:39AM
(#14526511)
Start by using done service discovery. That way service names stay the same but service implementations and locations can move.
Then ship the static list of names (should be short) and per-service credentials (highly highly recommended).
Another pattern is co-locating a proxy with your app. See e.g. linkerd on how to do that. This will also unify the handling of circuit breakers and connection pools across services - even without any shared code!
Right now, we have a bunch of microservices. Most of them talk to our shared infrastructure. We started with single configuration file, which has grown to monstrous proportions, and is mounted on every pod as a config map.
What would be the correct approach? Multiple configmaps with redundant information are just as bad, if not worse.