06-19-2020, 08:06 PM
First let's make some concepts clear.
A Windows service is a IW application with no GUI. What you call Stand Alone is the same application, but with a GUI which makes much simpler to debug. I don't recommend GUI-based apps in production, EVER.
Both Indy-based servers or Http.sys based servers can be deployed as windows services and GUI (stand alone) applications. You can convert from an Indy-based GUI application to a Http.sys service application (or any other configuration) changing exactly 2 lines of code in your DPR file.
The Http.sys application has better performance (better than anything hosted in IIS, for instance), but Indy is easier to debug and other things are simpler (e.g. installing certificates).
Regarding the hosting plan... if you are able to install a windows service on it with access to common windows infrastructure, I think you are good to go.
A Windows service is a IW application with no GUI. What you call Stand Alone is the same application, but with a GUI which makes much simpler to debug. I don't recommend GUI-based apps in production, EVER.
Both Indy-based servers or Http.sys based servers can be deployed as windows services and GUI (stand alone) applications. You can convert from an Indy-based GUI application to a Http.sys service application (or any other configuration) changing exactly 2 lines of code in your DPR file.
The Http.sys application has better performance (better than anything hosted in IIS, for instance), but Indy is easier to debug and other things are simpler (e.g. installing certificates).
Regarding the hosting plan... if you are able to install a windows service on it with access to common windows infrastructure, I think you are good to go.