DEV Community

Cover image for DBMS 3-tier architecture.✋✋✋✋
stalin s
stalin s

Posted on

1

DBMS 3-tier architecture.✋✋✋✋

DBMS 3-tier architecture divides the complete system into three inter-related but independent modules as shown in the above image(cover image).

Presentation layer / User layer✨✨✨: This tier is presented before the user who knows nothing regarding the other existing complex databases underneath. This tier can provide multiple views of the databases, generated by the application residing in the application tier.

Application tier✨✨: This is the middle-lined tier between the database and the presentation tier and acts as a connection between the end-user and the database. This tier holds the programs and the application server along with the programs that could access the database. This is the last layer that the users are made aware of . It provides a complete abstraction to the database layer.

Database tier✨: This tier holds the primary database along with all the data and the query language for processing. The relations of data with their constraints are also defined at this level.

Advantages:

✋ Enhanced scalability.
✋ data integrity.
✋ security.

Disadvantages:
✋ complexity of implementation and communication between client and server.

API Trace View

How I Cut 22.3 Seconds Off an API Call with Sentry 🕒

Struggling with slow API calls? Dan Mindru walks through how he used Sentry's new Trace View feature to shave off 22.3 seconds from an API call.

Get a practical walkthrough of how to identify bottlenecks, split tasks into multiple parallel tasks, identify slow AI model calls, and more.

Read more →

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay