In case of simplest mashup implementation, the web server handles all the responsibility of mashing; during the processing, the browser continues to sit and wait for the response. The typical Web-server mashup architecture is shown below:

The Architecture of Web server Mashups working the following steps:

1. the web browser uses HTTP to send request for a page to the server.
2. The web server constructs the page by connecting to the source or partner sites, which include Google, amazon, Yahoo, etc. In our example Amazon gets the first request from the browser using SOAP over HTTP.
3. The web server gets the SOAP response back from Amazon.
4. Our example has the second request being sent to Yahoo through REST.
5. The web server receives plain old XML over HTTP from Yahoo.
6. The web server now combines and rationalizes the data in the most suitable manner an sends the response back.
7. The data resulting from the web server is combined in an HTML format and the response is sent back to the browser.

Advantages:

1. Browser remains entirely separated from the partner sites, which are actually responding tot the request by providing data.
2. The web server itself works as an aggregator and proxy for the responses.

Disadvantages: 1. It involves a full page request being sent by the web server, thereby reducing scalability.