Ocelot
Ocelot copied to clipboard
Support dynamic routing configuration in Service Fabric
New Feature
Having to deploy Ocelot every time routing changes is tedious. Ocelot allows for modifying the routes using json reload but without deployment it is not really possible to do this either. This increases the cost of managing services in general. The target of this feature is to modify\extend Ocelot in a way that once deployed, ocelot can adapt to changes in services behind the scene.
Motivation for New Feature
Traefik supports something similar and that is the real motivation behind this feature. Today we are using Traefik but a few unrelated reasons are forcing us to move away from it.
Hi Ramjot! Are you still with Ocelot?
No, since this wasn't picked up and we absolutely needed dynamic discovery, we went with Traefik.
@RamjotSingh You are the author of the issue. You needed to contribute to implement your user scenario. If you don't use Ocelot now and you have no intention to contribute then I'm going to close...