Webfarms and Webgardens Explain both and their usage!
Each application pool runs with a single worker process (W3Wp.exe) by default. When an application pool runs with multiple worker process, it is called web garden.
You can set multiple worker process for an application pool as shown in below steps.
IIS :Default application->advance setting-> Maximum worker process [setvalue]
Pros of Web Garden:A Web garden share the requests which comes for that application pool and if one worker process fails to process a request then another worker process can continue to process that request.
Cons of Web Garden:There are some limitations with Web Garden. When you use session mode to “In Proc” with your application, it will not work properly as expected; since session will be handled by different worker process. For avoiding this issue; you should use session mode “Out Proc” having “Session State Server” or “SQL-Server Session State”.
When a web application is hosted on multiple web servers and access based on the load on servers, it is called Web Farm.
In web farm, a single application is hosted on multiple IIS server and these IIS servers are connected with the VIP (Virtual IP) with load balancer. Load balancer IPs is exposed to external world for accessing your web application. Hence, when a request comes to server from client, it first hits the load balancer, and then based on the traffic on each server; load balancer distributes the request to the corresponding web server.
//What you think ??//