VACS:Projects:Advanced:W4C
| Line 12: | Line 12: | ||
Finally, the W4C server's output is connected to a patented packet cleaner. The packet cleaner | Finally, the W4C server's output is connected to a patented packet cleaner. The packet cleaner | ||
washes the packet so that it appears dry and clean for transportation by the final pipe. | washes the packet so that it appears dry and clean for transportation by the final pipe. | ||
| + | |||
| + | ==High Availability== | ||
| + | |||
| + | [[Image:w4c_ha_monitor.jpg|thumb|128px|left|W4C HA Monitor]] The high availability of the platform is achieved by a state-of-the-heart and patented high availability monitor. The MTBF of the platform is proportional to the square root of the number of HA monitor. To achieve a 7 nines, it is necessary to have 3 HA monitors connected in parallel. | ||
| + | |||
| + | The HA sensor is the most sensitive element of the solution. Several HA sensors should be connected in parallel to achieve the stability of a single HA monitor. The signal is amplified and converted to a digital signal. You can adjust the HA monitor sensitivity with a potentiometer. | ||
| + | |||
| + | ==High Performance Server== | ||
| + | |||
| + | [[Image:w4c_server.jpg|thumb|128px|left|W4C Server]] The server uses a multi-threaded and multi-pipe architecture. Requests are queued in a big receptacle. The queue length depends on the volume of the receptacle. A pump extracts requests from the receptacle and pushes them with 100bar force to the multi-thread expansor. The expansor handles the requests by dispatching them to a multi virtual machine that executes the web application. | ||
| + | |||
| + | The multi-virtual machine has a sustained performance to handle the 100Gb traffic if necessary. | ||
| + | This is in fact proportional to the inverse of the available memory. Unlike most virtual machines, the less memory you have the better performance (this is also a patented solution). | ||
| + | |||
| + | ==SOA== | ||
| + | |||
| + | [[Image:w4c_wsdl.jpg|thumb|128px|left|W4C SOA]] The W4C platform follows the latest SOA models. You may find some information at [http://www.service-architecture.com/]. | ||
| + | |||
| + | |||
<gallery> | <gallery> | ||
</gallery> | </gallery> | ||
Revision as of 12:13, 10 September 2006
This site is running on a small PC (VIA miniITX board) running GNU/Linux. Because it was small, and our flat had not place, the PC was located in the WC.
Below is a new computer architecture that is intended to supersede the performance of high end systems sold by big companies (Sun, [1], ...). Its novel architecture will bring you the performance, scalability and high availability (7 nines!!!).
Contents |
Overview
The firewall connects to a yet modern and high performance connector architecture that redirects the request to the web server. This connector architecture is faster than any enterprise solutions that exists on the market. It achieve more than 100K requests per second and can be extended by adding connectors in parallel (W4C farms).
Finally, the W4C server's output is connected to a patented packet cleaner. The packet cleaner washes the packet so that it appears dry and clean for transportation by the final pipe.
High Availability
The HA sensor is the most sensitive element of the solution. Several HA sensors should be connected in parallel to achieve the stability of a single HA monitor. The signal is amplified and converted to a digital signal. You can adjust the HA monitor sensitivity with a potentiometer.
High Performance Server
The multi-virtual machine has a sustained performance to handle the 100Gb traffic if necessary. This is in fact proportional to the inverse of the available memory. Unlike most virtual machines, the less memory you have the better performance (this is also a patented solution).
SOA
