Abstract
It is desirable to have a Distributed Database Management System (DDBMS) whose behavior and control is as identical as possible to that used in single site database management systems. We call this notion site autonomy. Preserving the autonomy of sites which join a DDBMS network is essential to the peace of mind of its managers and users, and more technically, is essential in an environment where sites and communication lines fail. To achieve resilience to failures of sites and communication lines (these are indistinguishable from one site's viewpoint), there can be no reliance on centralized functions or services. This means no global dictionary, no global information collector for deadlock detection, and no broadcast of local events such as file creation or addition of a new site. Aside from these prohibitions, this goal of site autonomy also implies that sites should perform their own compilation, their own binding of print names to internal names, their own decomposition of compound objects (such as relational views), and their own authorization checking. This talk discusses the concept of site autonomy in further detail and discusses several specific issues on which the site autonomy philosophy has an impact.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
