Environment infrastructure
Prev | Chapter 11. Berkeley DB Transactional Data Store Applications | Next

## Environment infrastructure

When building transactional applications, it is usually necessary to build an administrative infrastructure around the database environment. There are five components to this infrastructure, and each is supported by the Berkeley DB package in two different ways: a standalone utility and one or more library interfaces.

- Deadlock detection: db_deadlock utility, DB_ENV->lock_detect(), DB_ENV->set_lk_detect()
- Checkpoints: the db_checkpoint utility, DB_ENV->txn_checkpoint()
- Database and log file archival: the db_archive utility, DB_ENV->log_archive()
- Log file removal: db_archive utility, DB_ENV->log_archive()
- Recovery procedures: db_recover utility, DB_ENV->open()

When writing multithreaded server applications and/or applications intended for download from the Web, it is usually simpler to create local threads that are responsible for administration of the database environment as scheduling is often simpler in a single-process model, and only a single binary need be installed and run. However, the supplied utilities can be generally useful tools even when the application is responsible for doing its own administration because applications rarely offer external interfaces to database administration. The utilities are required when programming to a Berkeley DB scripting interface because the scripting APIs do not always offer interfaces to the administrative functionality.

Prev | Up | Next
Nested transactions | Home | Deadlock detection