DBM::Deep's initial mission was to provide a Perl interface to disk-backed storage. It did this so well that programs don't even know they're working with disk-backed data structures. Combine this with transactions and you have the ability to treat a data structure transactionally. In other words, "lockless atomic concurrent access to data." That this lockless concurrent access occurs on disk is undesirable, but transparent to the program. Adding the ability to do this in-memory vs. on disk is an optimization, not a specification.