As defined in Internet Information Services (IIS) an application Pool is a collection of one or more URLs that are serviced by one or a set of worker processes. After installation of SharePoint, open IIS Manager. You will notice application pools in iis.
You must select an existing Application Pool or create a new pool whenever you create a service or web application in SharePoint Server.
application pools in iis allow multiple SharePoint websites to run on a single server without the processes or code in one site interacting with any other sites. This is primarily a security benefit, since any outside intrusion on one site is isolated. Also, problematic or poor code running on one site is isolated so that other sites on the server are unaffected. For these reasons, you should plan to use dedicated application pools to isolate authenticated content and separate applications that contain password information.
we can run powershell command to get all application pools.
Get-IISAppPool
we can search one or more application pool directly by running the below command.
Service Applications in SharePoint are associated with web applications, and specific services are typically deployed as needed in a particular farm. Only deployed services are referred to as service applications. This is a huge advantage in terms of conserving resources and optimizing performance. For instance, a specific web application can be configured to use only the services it needs. The number of service applications that exist is vast, and, as third-party vendors can create their own services for SharePoint Server. A list of services includes the following:
You can set up a single service application to be shared among multiple web applications or deploy multiple instances of the same service across a farm and, in some cases, across multiple farms. Also, there is no limitation regarding the number of services that can be deployed in any single farm. A typical planning scenario requires that you either set up services to share across multiple web applications or isolate an individual service to one or a limited number of web applications. We can publish below service applications across the farm.
Business Data Connectivity
Machine Translation
Managed Metadata
User Profile
Search
Secure Store
Navigate to “Central Admin -> Application Management ->Manage Service Applications” and click on “New” from ribbon to see the list of service applications available.
you can use powershell command to get the list of service applications
For every service application there is a service associated with it which you can from central admin by navigating to “Central Admin -> Application Management -> Manage Services on Server”.
Alternatively you can use the powershell command as below
Get-SPServiceInstance | Format-Table -wrap
Get-SPServiceInstance | Where {$_.Status -eq "Online"} | Format-Table -wrap
Similarly we can start the service instance by running the below command.
Group of servers in a single location represents one server farm. It lies in the highest-level element in design structure, and each server farm offers physical isolation of your resources from other server farms. We can be deploy sharepoint in one farm or across multiple server farms depending on requirements. Below points represent various points based on which can decide whether to to deploy on a single farm or across multiple farms :
Needing multiple dedicated services farms to accommodate heavier use of specific services
Having separate operational divisions of responsibility in your organization requiring isolation of resources
Funding that is dedicated for specific purposes requiring more than one farm
Using separate data center locations
Satisfying any industry or legal requirements for physical isolation between sites for your organization
Using multiple server farms to enhance performance and scalability as well as licensing requirements and publishing environment goals
if there is plan on sharing multiple resources in SharePoint environment, a single server farm is sufficient. If requirement is like services and resources to be isolated for any of the circumstances listed above, we require several server farms and probably one server farm per isolation requirement.
In an enterprise-level environment with its needs operating and changing dynamically on many levels, planning for multiple server farms is the better option, assuming isolation is weighted more heavily than budget concerns.
