dotnet/orleans

Avoid opening any ports for single instance ASP.NET Core co-hosted apps

Open

#7,023 opened on Mar 11, 2021

View on GitHub
 (1 comment) (4 reactions) (1 assignee)C# (10,777 stars) (2,123 forks)batch import
help wanted

Description

Company I work for has created many small apps using Orleans. All of them have had ASP.NET Core and Orleans running in same app and we have run them in same IIS. So they are all single instance apps. Currently there is no way to tell Orleans not to open any ports. I think currently Orleans opens ports 11111 and 30000. So what I'm asking is making Orleans little bit nicer for single instance setups by adding way to opt out from any distributed features.

PS @ReubenBond responded in Gitter that I should write issue about this.

Contributor guide

Tech stack
csharp
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of Orleansfamiliarity with ASP.NET Core co hosting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the current port configuration in Orleans, specifically how ports 11111 and 30000 are opened. Look into the SiloOptions class and the startup process for co hosted ASP.NET Core apps. The goal is to add a configuration option (e.g., 'DisableDistributedFeatures' or 'NoPorts') that prevents port binding. Reference the Gitter conversation with @ReubenBond for additional context. Ensure the implementation does not break existing functionality for multi instance deployments.