Three-Tier Architecture
Three-Tier software architecture (Figure 1.1) started in the 1990’s to overcome the limitations of two-tier architecture (Figure 1.2), such as that it is not scalable as each client requires its own connection to the database. In a three tier architecture the middle tier lies between the User interface (Web Application) and the Data Management (Server) and provides process management where business logic and rules are executed. This makes the application highly scalable. Where two tier architecture (Client/Server) can support a max of 100 connections, which would be good for a Medium sized organisation, the three tier architecture allows for a couple of hundred connections. Figure 1.1 …show more content…
This tier is responsible for performing complex business logic.
Data Storage:
This tier provides database management functionality and is dedicated to data and file services. As such this tier contains the file system and the database. Further, because the database will contain only information regarding files, the actual file system containing the media content resides in the Data Storage tier too.
The diagram below (Figure 1) show’s a “light weight” architecture that uses REST.
One of the benefits of this architecture is that the data services are completely decoupled from the applications that consume them. This means, in real live there could be one team working on the web client and another team working on the Spring Boot Micro Service.
Another advantage is that there could be as many Web Clients or Mobile clients as necessary, which makes the access very versatile.
In old school apps the view and server side logic were often interleaved e.g. JSP/Servlets. Using the architecture shown here you expose a set of services that anyone can consume.
Light Weight