Editing Berkeley DB (section)

==Architecture==
Berkeley DB has an architecture notably simpler than [[relational database management system]]s. Like [[SQLite]] and [[Lightning Memory-Mapped Database|LMDB]], it is not based on a [[Client–server model|server/client]] model, and does not provide support for network access{{snd}} programs access the database using in-process [[Application programming interface|API]] calls. Oracle added support for SQL in 11g R2 release based on the popular SQLite API by including a version of SQLite in Berkeley DB (it uses Berkeley DB for storage).<ref>{{cite web|title=Twitter / Gregory Burd: @humanications We didn't r ...|url=https://twitter.com/gregburd/statuses/10979336891}}</ref>

A program accessing the database is free to decide how the data is to be stored in a record. Berkeley DB puts no constraints on the record's data. The record and its key can both be up to four gigabytes long.

Berkeley DB supports database features such as [[ACID]] [[Database transaction|transactions]], fine-grained [[Lock (computer science)|locking]], hot [[backup]]s and [[replication (computer science)|replication]].