PALM-3000 Database Architecture Highlights

1. PALM-3000 Database Architecture Highlights • Component-based architecture • AODR: Data recorder component. • AODS: Data server component. • Simple function-call API for all database operations • Simple key/value lookups. • No query language to parse. • No execution plan to produce. • Not a relational database. • Support for C, Java, and in Phase II, Perl and IDL. • Enable flexibility and control. • Embeddable, in-memory, not client-server • Components may link directly into the application. • Run in the same address space as the application. • No inter-process communication required for database operations. • Data stored in application-native format • No translation or mapping required. • Configurable Cache • Provides fast access to a cache of database pages, while ensuring dirty pages are written back to the file system. • High concurrency • Multiple processes (readers and writers) across machines or on a single machine, or multiple threads in a single process, can all use the same database concurrently. • Transactions and recovery • Permit multiple changes appear at once. • Guarantee the database is complete and usable after a system or application crash. • Have ACID properties (Atomicity, Consistency, Isolation, Durability) • Provide reliability and data integrity. • Hot backups • Support database backups while the database is in use, using standard UNIX utilities (dump, tar, cpio, cp…) Nothing more than key/value lookups with cache management plus transaction and locking support.