API review for Service Discovery

[danmoseley]

Proposal: dotnet/aspnetcore#53715

[TimHess]

Has there been any planning or experimentation around providing a common interface for use with service registries that allow or even require the client to register, or is this feature expected to be limited in scope to the discovery side only?

Example registries would include at least Consul and Eureka

[codymullins]

@danmoseley is there any existing documentation around the Service Discovery API? This would be useful to have in situations where the client (e.g. Blazor WASM) needs to exchange the service name with the actual endpoint URL.

[danmoseley]

@codymullins missed your comment sorry. @ReubenBond can describe what we have and what we plan.

[ReubenBond]

@TimHess good question. We considered it and decided that we would not add a common service registration interface in the initial release. It would be worthwhile to explore the idea, though, so if you'd like to open an issue with requirements and a proposal, that would be greatly appreciated.

@codymullins Aside from the API doc comments, there are the package READMEs and the conceptual docs: https://learn.microsoft.com/en-us/dotnet/aspire/service-discovery/overview

For your specific scenario, resolving backend services from a Blazor WASM app, you likely need some way to propagate the configuration to the Blazor WASM app. Aspire uses environment variables to configure service discovery. You can also use appsettings.json, which Blazor WASM loads from wwwroot (docs: https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/configuration?view=aspnetcore-8.0). The abovementioned README shows how you can configure service discovery in your appsettings.json file in this section: https://github.com/dotnet/aspire/tree/main/src/Microsoft.Extensions.ServiceDiscovery#resolving-service-endpoints-from-configuration. I hope that helps.

[davidfowl]

Putting this in preview4