ThreeMammals/Ocelot

Support dynamic routing configuration in Service Fabric

Open

#939 opened on Jun 24, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C# (1,617 forks)batch import
MVPService DiscoveryService Fabrichelp wantedlarge effortproposal

Repository metrics

Stars
 (8,137 stars)
PR merge metrics
 (Avg merge 10d 13h) (4 merged PRs in 30d)

Description

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.

Contributor guide