A DBMS design is based on its architecture. It can be hierarchical or hierarchical or centralized. It is possible to see the architecture of a DBMS as either single or multi-tier. The n-tier architecture divides the entire system into n modules that are related but separate, which can be modified, changed, modified or replaced independently.
The DBMS is the only entity in a 1-tier architecture where the user sits directly on the DBMS and uses it. Any improvements made here will be carried out on the DBMS itself directly. For end-users, it does not have handy tools. Designers and programmers of databases usually prefer to use a single-tier architecture.
If the DBMS architecture is 2-tier, it must provide an application by which to access the DBMS. Programmers use a 2-tier architecture where, via an application, they access the DBMS. Here, in terms of operation, design and programming, the application tier is totally independent of the database.
Based on the complexity of the users and how they use the data present in the database, a 3-tier architecture divides the tiers from each other. It is the architecture most commonly used to design a DBMS.