Pro and Cons, running PSU as service vs host on IIS vs proxy via IIS

PowerShell Universal
1 
Product: PowerShell Universal
Version: 5.6.10

my current config in production is PSU 5.6.9 hosting on IIS 10, with Windows auth enabled, it works.

But, I am a person always looking at new possibilities :slight_smile:

In my test env, I have PSU 5.6.10 running as service at port 5000 and IIS 10 as proxy to server PSU at HTTPS/443, using windows auth, it works as well

I have also tested running only PSU as service at port 5001 with certificate configured and HTTPS. and it seems working fine.

Question is, we have below 3 config choices:

  1. PSU running as service, port 443, HTTPS enabled via appsettings.json, Windows auth working
  2. PSU running as service, port 5000, HTTP enabled via appsettings.json, IIS acts as proxy to HTTPS 443, windows auth working
  3. PSU hosted in IIS, HTTPS 443, Windows auth works

which of those config is the most stable, or give most performance or most secure or easiest to maintain?