When developing web applications one challenge is web server mocking. If you are writing an application that ultimately relies on a connection to a web server how do you effectively stand up a mock server? In the past many developers would rely on the standards, Microsoft IIS and Apache for example, which are separate applications running locally or on a development server. But the big issue here is dynamically changing their configurations – a primary requirement of mock environments. This is hard to achieve since these are separate applications tightly integrated with the local operating system and keep under lock and key by rigid security protocols.