Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!munnari.oz.au!bruce!goanna!wren!hao
From: hao@wren.cs.rmit.OZ.AU (Hao Hong Nguyen)
Newsgroups: comp.databases
Subject: Need information on DBMS architecture
Message-ID: <5274@goanna.cs.rmit.oz.au>
Date: 16 Apr 91 08:50:50 GMT
Sender: news@goanna.cs.rmit.oz.au
Lines: 28


The common architecture of a relational DBMS is to have two layers: the
front-end process and back-end process. The front-end process may be a form
interface, a textual command language (eg SQL) or a user application. The
back-end process (also called the kernel) is a common program which contains
the query evaluator, indexing code and accessing to raw data stored on disk.

As my knowledge, on an Unix system, the kernel and the
front-end can communicate through socket, pipe or shared memory.
Is there any other DBMS architecture ? and how how different compenents of a
DBMS communicate to each other ?

The reason I ask for this is that my group is implementing a research
DBMS and find out that the communication overhead is quite
siginificant.

I am looking for any papers or books to talk about these thing formally. I will
be appreciate for any help.


-------------------------------------------------------------------------------
Hao Nguyen,                        ACSNET: hao@goanna.cs.rmit.OZ
Key Center for Knowl. Based Sys.,  INTERNET: hao@goanna.cs.rmit.OZ.AU
Victoria University of Technology, JANET: hao%au.oz.goanna@uk.ac.ukc
RMIT Campus,                       BITNET: hao%goanna.cs.rmit.OZ.AU@relay.cs.net
Dept. of Comp. Sci.,               UUCP: ..!uunet!goanna.cs.rmit.OZ.AU!hao
GPO BOX 2476 V,                    Phone: +61 3 660 2992
Melbourne, 3001, AUSTRALIA         Fax:   +61 3 662 1617