"ReverseProxy" is the simplest and most practical way is to support powershell !

Microservices, docker and asp.net core applications require api gateways.app need add and delete backends with commands.

Performance should not be a priority,
The configuration file format should not be a priority.
Supporting the command line is the priority.

"ReverseProxy" is the simplest and most practical way is to support powershell !
Can ReverseProxy support command interface support?
If the reverse proxy can support command interface support, it is excellent.

powershell 7.1 preview uses .net core 5,
powershell 7.0 uses .net core 3.1,
Powershell uses ConvertFrom-Json to convert json to .net hash table object.

I think the simplest and most practical way is:
release ReverseProxy dll and make a powershell module to https://www.powershellgallery.com/

Use the powershell command to add .net object:
Add-ReverseProxy -name 'server1' -ipaddress '192.168.0.1'
Remove-ReverseProxy -name 'server1' -ipaddress '192.168.0.1'

and then sync "server1.json" to the disk configuration file every 10 seconds. The format of the configuration file is not important.

Start-ReverseProxy -listenip '1.2.3.4'
Stop-ReverseProxy

Add-UrlRewrite -name 'aaa' -base 'http://192.168.0.1' -url '/a/b' -Rewriteto 'xxx'
Remove-UrlRewrite

by the way:
Recently, my project needs a reverse proxy. When will it be released?