Application Architecture in DBMS

 Database applications are usually divided into two or three parts.

In a two – tier architecture, the client machine uses query language statement and invokes database system functionally at the server machine. For interaction between the client and the server, application program interface like JDBC and ODBC are used.

In a three – tier architecture, the client machine acts as a front end and do not directly call database. Instead, it communicates through forms interface with an application server, and the application server communicates with the database to access data.


Figure – 1: Two – tier and three – tier architecture





Comments

Post a Comment

Popular posts from this blog

A university registrar’s office maintains data about the following entities: (a) courses, including number, title, credits, syllabus, and prerequisites; (b) course offerings, including course number, year, semester, section number, instructor(s), timings, and classroom; (c) students, including student-id, name, and program; and (d) instructors, including identification number, name, department, and title. Further, the enrolment of students in courses and grades awarded to students in each course they are enrolled for must be appropriately modelled. Construct an E-R diagram for the registrar’s office. Document all assumptions that you make about the mapping constraints.

Image
Read more

Consider a database used to record the marks that students get in different exams of different course offerings.

Image
a. Construct an E-R diagram that models exams as entities, and uses a ternary relationship, for the above database.  b. Construct an alternative E-R diagram that uses only a binary relationship between students and course-offerings. Make sure that only one relationship exists between a particular student and course-offering pair, yet you can represent the marks that a student gets in different exams of a course offering. (a) (b)
Read more