Some applications split across microservices might require that each single development environment should be running at the same time so they consume each other to produce the final desired effect.
Right now we can handle this by manually changing HTTP mapped ports, adding some more aliases, and rely on $KOOL_GLOBAL_NETWORK (kool_global) to communicate.
This is a recurring use case that we should consider, maybe, a more developed and complete proposition on how to deal with such a scenario.
Some applications split across microservices might require that each single development environment should be running at the same time so they consume each other to produce the final desired effect.
Right now we can handle this by manually changing HTTP mapped ports, adding some more aliases, and rely on $KOOL_GLOBAL_NETWORK (
kool_global) to communicate.This is a recurring use case that we should consider, maybe, a more developed and complete proposition on how to deal with such a scenario.