Three tier architecture is a pattern, or order of operations that pertains to the manner in which we go about building an application or program. Each tier will run on it's own infrastructure, and can be developed simultaneously. A three tier architecture design benefits our code organization, and scalability, as well as providing a way in which we can visualize the interaction between different systems that help bring our application to life. The three tier architecture system consists of the Client Tier, Business Logic Tier, and the Data Tier. These tiers are also referred to as layers, the presentation layer, the application layer, and the database layer. Before we get into the depths of three tier architecture and it's layers, it is good to have a basic understanding of one and two-tier architectures.
The first tier is the client tier, which is considered the presentation layer. This layer considers your front-end framework, or how your app to be displayed, which can be via laptop, mobile phone, or even a smart TV! It is called the client/presentation layer because this is the layer that your clients will interact with, and where the magic of your code will be presented, such as your web browser. On this layer, the client will see text boxes, and buttons, and will enter interact with your page via clicking on things and entering information, and all of this information will later be handled by our second tier, which is called our business logic tier or application layer.
Business Logic Tier // Application Layer
So this is essentially the 3 tier architecture. The first tier being where you enter information, the second tier being where this information is handled, and the third tier being where the data for the second and first tier is stored.
SOCIAL SHARE CARD GENERATOR