ThreeMammals/Ocelot

Support dynamic routing configuration in Service Fabric

Open

#939 opened on 2019年6月24日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)C# (8,137 stars) (1,617 forks)batch import
MVPService DiscoveryService Fabrichelp wantedlarge effortproposal

説明

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.

コントリビューターガイド

技術スタック
csharp
領域
backendapi
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Familiarity with Ocelot codebaseUnderstanding of Service FabricExperience with .NET
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
5
調査方針
Investigate how Traefik implements dynamic routing for Service Fabric. Review Ocelot's configuration reload mechanism and service discovery integration. Identify key areas in the codebase (e.g., FileConfigurationController, ServiceFabricServiceDiscoveryProvider) that would need modification to support real time routing updates without redeployment.