Web Hosting and defining an Application Service, what are the best practices?

[TaylorJ]

I have multiple websites that are hosted on the same group of servers, would this be individual application services or one application service with all sites as offerings.. looking for insight and best practices at this time.

[Kim Rasmussen]

If they serve different business purposes then I would recommend to have seperate Application services.

The Websites should have individual Entry addresses, and you should be able to start from there.

If you were to use Service Mapping the Entry URL is also where you normally start, Service Mapping will include the apps - but not the servers in the map.. The servers are related to the app service through the app. 

[TaylorJ]

Here is my question, maybe this will help 🙂

I have 3 endpoints for 3 unique sites hosted on the same webserver infrastructure (see example).  Would the best practice be to have one application service based on 1 set of infrastructure for service mapping and alerting or would the best practice be to create separate application services and perform service mapping of each individual service even though the infrastructure is the same?

[Kim Rasmussen]

I believe that you need to take a step back and look at your business applications, and then model your Application Services from there.  Application Services is meant to be the Mapping between the Technology Infrastructure to the Business it serves - not just reflect the technology.

With out knowing you full setup, from the schema you have included it looks to me that it is 3 different Business app/service/offering and therefore you should have 3 App Services even though they currently share the same technology infrastructure. For starters do the services have individual Endpoints and probably some sort of IIS Site or Pool configuration.

Also when you look at in the larger context. As an example; There will be Code that vary from the 3 services and you might need to do a change to one App without doing anything the the other Apps. 

[lanoharaft]

Managing sites separately makes it easier to scale and maintain them individually. You can apply updates, monitor performance, and troubleshoot issues more effectively when each site is isolated within its own application service.

As for hosting options, I've come across DMCA Ignored Hosting, which offers solutions that align well with this approach. They provide robust support for managing multiple applications on shared servers while ensuring each site maintains its integrity and performance. It's worth exploring their services if you're looking for flexibility and reliability in hosting multiple websites.