MXCuBE web application

Rationale

Architecture

The fundamental principle behind any web application resides in the client-server model of the web: a web application is made of code running both on a server and on a web browser (thin client). Essentially, web applications relies on a "front-end part" and a "back-end part". This dichotomy lend web applications to a n-tier architecture by nature.

For example, the more classic web application has a 3-tier architecture:

• Presentation (client side)
• Storage (server side)
• Application/Business logic

For any web application the presentation tier is always on the client, since the application is rendered in the web browser, where user interaction takes place. The other parts can be spread between server and client. In particular, for the application logic the full field from all in the server to all in the client is possible. Indeed, nowadays web browsers feature very powerful scripting engines (Javascript) and can perform almost all the tasks of any decent programming environment.

Moreover any non-trivial web application requires some communication protocol to exchange data between the client and the server.