Introduction
This article is the second part of the SharePoint series. You can read the first part here at Learn SharePoint In Series-Part One-Introduction. In the previous article, I have described the introduction of SharePoint and some basics of SharePoint such as history, and choosing between SharePoint and other technology. So, in this article, I am moving one more step ahead.
In this article, I am going to cover the following topics.
- Background of SharePoint
- SharePoint Web Application in Terms of SharePoint on Premises Server
- SharePoint Web Application in Terms of SharePoint Online
- Creating Web Application
Background of SharePoint
SharePoint is based on the .NET Framework. SharePoint requires a Windows Server Operating System. SharePoint uses SQL Server Database to maintain the contents. In SharePoint terminology, the SQL Server Database is called a Content Database. The users and groups in SharePoint are managed in Active Directory.
SharePoint Web Application in Terms of SharePoint on Premises Server
We know that every .NET web-based application needs an IIS Server for hosting. We create an Application Pool and a Website in IIS to host the .NET Framework web application. In a similar way, when we create a SharePoint Web Application, SharePoint creates an application pool and IIS websites and hosts precompiled websites in that IIS under created IIS site. SharePoint Web Application is the entry point for SharePoint.
In a single SharePoint Server, we can have only one SharePoint Web Application without a port number in the URL (Default port i.e. 80). Example: We can create only one SharePoint Web Application with http(s)://domain. When we create another Web Application it creates with URL such as http(s)://domain:port (5555). However, we can extend the SharePoint Web Application to support multiple Web Applications on Port 80.
As per Microsoft Limits and Boundaries description, we can have 20 Web Applications per SharePoint Server. However, this is not the hard limit. These are Microsoft-supported limits. We can create more Web Applications but that will affect the performance of the SharePoint if the SharePoint Server is not capable of handling the bigger loads.
If we talk in terms of Content Database, then a single SharePoint Web Application can have a maximum of 500 Content Database. In a case when you have large data, let’s say more than 1000 GB, Microsoft doesn’t recommend you to store all the data in a single Content Database. Microsoft recommends 200 GB of content per content database. So we can divide the contents into various content databases. So in other words, we can say that a single Web Application can have more than 1 content database.

Join the conversation! Your thoughts help the community grow.