SharePoint 2010 Versions: http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx
Licensing Q&A: Determining Your Licensing Needs: http://sharepoint.microsoft.com/en-us/buy/Pages/Licensing-Details.aspx
Try Office 365 for free for 30 days: http://www.microsoft.com/en-us/office365/free-office365-trial.aspx#fbid=Z2H52GGA8QQ
Planning for server farms (SharePoint Server 2010): http://technet.microsoft.com/en-us/library/cc262936.aspx
Performance and capacity management (SharePoint Server 2010): http://technet.microsoft.com/en-us/library/cc262971.aspx
For intranet/extranet we need Client Access Licensing(CAL) Device/User based. In Production all instances of server needs SharePoint licensing. For development/staging server MSDN licensing is required.
In orginzation there can be 2 or more farm servers, 1. Intranet 2. Internet. Both have diffent licensing. We can install 2 license on the same farm. Extranet can include in either Intranet or Internet licensing. Intranet needs CAL.
1 farm can be dedicated to MYSITE if the users creating mysite are huge.
Small Farm - 2WFEs, 1 App server, 2 DB server(Search DB, other)
Medium Farm - Multiple WFEs, 2 App servers(Combined Query and crawl server, other services), 2 DB(search DB, other)
Large Farm - Mulitple WFEs(Seperate group for incoming request, group for crawling and administration), 4 group of app server(crawl, query, other, running sandbox code), 3 group of DB server(Search Server, Content DB server, others)
1 WFEs = 10,000 users, App server and DB depends on search and data.
Site collection are
1. Orgainzational sites: Combination of team site and publishing content site
2. Application sites: User interaction such as timesheet application
3. Publishing site: There is authorizing server, staging server and production server all in different web application for publishing content.
For single site collection DB cannot be more that 100GB(best practice) Here we have to split site collection into mulitple site collection if DB size goes more than 100BG.
By default every web application creates its own content db. While planning creating different site collection helps for scalability because if content db reaches 100GB we can move site collection to new content db by using Move-SPSite command.
Web application is used to redirect incoming http request to SharePoint sites. We should always consider below additional overheads before creating new web application.
1. Additional RAM required per Web app (even with 0 users) > more hardware required.
2. Timer jobs (around 30 per Web app, several of which run every few minutes (e.g. alerts & workflow) and many which run daily (e.g. workflow processing and gradual site deletions)
3. Content databases - per SQL instance limit, backup concerns, storage space
4. Application pools if isolating for security reasons
5. IIS sites > administrative overheads (host headers, IP addresses, SSL certificates, Web configuration files, assemblies).
6. Other operational overheads: DNS / request routing; SharePoint solution management
Multi-Tenancy can be done to web application as well as site collection. In 2010 we can do alternate access mapping to site collctions as well.
We can have 300 databases per web application.
Extend Web applications when you want to change authenication type or give different set of users different authentication and URL