| The Definitive Guide to Db4o Contributor(s): Paterson, Jim (Author), Edlich, Stefan (Author) |
|
 |
ISBN: 1590596560 ISBN-13: 9781590596562 Publisher: Apress OUR PRICE: $52.24 Product Type: Hardcover - Other Formats Published: June 2006 Annotation: To satisfy the demand for 24/7 information access, applications available in airport and conference kiosks, and in the mobile, gaming, and medical industries, provide consumers data access wherever they are. But it's essential that fast availability not be traded for quality performance. A prominent solution for managing the data in these applications and devices is db4o--the open source object database native to the Java and .NET platforms. Highly reliable and scalable, db4o cuts down on development time by smoothly integrating into the system, cutting out the otherwise costly object-relational mapping typical of larger applications. "The Definitive Guide to db4o" is the first book to comprehensively cover this project in detail. You will learn about all relevant topics, including installing and configuring db4o, querying and managing objects, performing transactions, and replicating data. To aid newcomers to the topic, early chapters cover object database fundamentals, as well as technical considerations and migration strategies. The book is complete with numerous C# and Java examples, so you'll be able to follow along regardless of your chosen language. |
| Additional Information |
| BISAC Categories: - Computers | Databases - General - Computers | Software Development & Engineering - General |
| Dewey: 085.756 |
| Physical Information: 1.42" H x 7.33" W x 10.45" (2.42 lbs) 484 pages |
| Descriptions, Reviews, Etc. |
| Publisher Description: Sometimes we make things more difficult for ourselves than they really need to be. Programmers are no exception to this. For example, those of us of an object-oriented persuasion devote time and expertise to creating a model of a problem domain in terms of objects. We produce solutions that model real-world objects and that are highly extensible and reusable. And then we decide that we need those objects to stick around after the program stops, so we go ahead and create another, totally different model, just so that we can use a database. Our carefully designed objects are then chopped and squeezed to fit this new data model. In fact, most developers would argue that object persistence is a fundamental problem that has yet to be adequately solved. While there are frameworks that hide some of the details of the mismatch between object and data models from the programmer, none of them convi- ingly make what should be a simple job really simple. We held the same opinion, until we found out about db4o. db4o--the database for objects--simply stores native objects. "Native" means that these are the objects that your C# or Java program creates, stored exactly as they are. There's no need to create a database schema, no need to map objects to tables, no need to do anything really, except store objects. |
