Over the past couple of years I have spent significant amount of time to asses and plan enterprise web platform on Windows 2008 and Windows 2008 R2. I want to share my experience and recurring theme about setting up Web Platform and “Ecosystem” for Microsoft Web stack.
Web Server: Internet Information Service (IIS) is the Web server that is centrepiece in the echo system. It provides a security-enhanced, easy-to-manage web server for developing and reliably hosting web applications and web services. IIS provides process isolation (Worker Process) that acts as security and admin boundary to separate application and manage resources. True power of IIS lies within its modular architecture to enables us to interact with the way IIS process request/response and enhance IIS functionality.
Web Platform installer (WebPI): Web Platform Installer (Web PI) makes it easy for you to download, install, and keep up to date on latest software components of the Microsoft Web Platform for development and application hosting. Think about it as a gateway to connect and interact with other parts of web ecosystem and/or it app store for IIS that allows you to download various modules to enhance IIS functionality or single-click application provisioning and configuration.
Web Deploy (WebDeploy): Web Deploy is an integration component and bridge between Application Developers and server administrator. It allows developers to publish/deploy application on server farm and server administrator to synchronize the web-content and configuration to multiple servers. I view Web deploy as a framework for synchronization not only for files and folders but various component like GAC, COM, Registry etc.
Web Farm Framework (WFF): It is a framework to effectively manage your web servers. This framework binds above component together to effectively build web farm that administrator can manage and maintain with least possible administrative overhead. This framework takes care of installation of infrastructure component via WebPI and application deployment by utilising WebDeploy underneath as a provider.
And as always there is more to add in the list but for now this is sufficient. In next post I will talk more about “Application Stack” on Microsoft Web Infrastructure.