If we consider the potential for actual-time updates via generation of ready chunks of content material on the server side and updates of the consumer (by way of AJAX, WebSockets), plus design with partial adjustments of a web page, we’ll transcend this architecture.
Use of the extended sort of this structure (when knowledge are transferred as JSON) lowers the site visitors between the client and the server, but adds an abstraction level to the appliance: retrieval from database -> knowledge processing, serialization in JSON -> API: JSON -> parsing of JSON -> binding of information object on the consumer to HTML.
This setting nonetheless has two single points of failure (load balancer and master database server), but it surely offers the the entire different reliability and performance advantages that were described in each section above. NGINX Plus is a particularly environment friendly reverse proxy and cargo balancer when deployed in entrance of web and software servers, with translation modules for a number of types of software server including FastCGI and SCGI. Personally I do not prefer to ask questions like Difference between Application Server and Web Server. All the web logic is on the client side, there is no such thing as a content material generation on the server.