Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!uunet!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.databases Subject: Needed: Literature on two-phase commit, distributed databases, etc. Message-ID: Date: 29 Jan 91 19:33:40 GMT Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Organization: GE Corp. R & D, Schenectady, NY Lines: 22 I am looking for literature describing distributed databases, and the problems inherent in them. My brother is working for a company who thinks building a distributed database is simple. As he will have to maintain this product, he is very concerned! The developers (if you can call them that) want to hack together something that has pieces of the database distributed across different machines. They don't seem to understand concepts like two-phase commit, and how to keep distributed databases from getting out of sync. And if they do, how to recover. The answer is "Oh, I doubt that would happen." Therefore I am looking for some literature that describes all of the problems a distributed database should watch out for. Or else a list of features such a database should have, with an explanation WHY these are needed. Send me E-mail - to keep the noise level down. Thanks. -- Bruce G. Barnett barnett@crd.ge.com uunet!crdgw1!barnett