Welcome, let's DB->open() a conversation about data storage.
By Gregory Burd on Jul 21, 2009
Here you will find articles about Berkeley DB products, interesting use cases, and fun factoids to keep you informed and hopefully interested in Berkeley DB products.
The term "database" conjures up thoughts of SQL, tables, and client/server architecture. This hasn't always been true. Database is not just another way of saying "SQL" and it's not always a synonym for RDBMS (relational database management systems). In today's complex distributed and diverse software ecosystem there are many new and divergent requirements for data storage. A sizable portion of those cases don't have any need for SQL, but they do need transactions, recovery, concurrent access, replication, fail-over, hot-backup, and all the other core features of an RDBMS. There is a growing awareness that non-relational (aka NoSQL) storage solutions have an important role to play in systems of all shapes and sizes.
Of course here within Oracle, and especially within the Berkeley DB group, we've known this for a long time. We've been working for over a decade on a database engine that has the qualities found at the core of most modern database products (relational, object, hierarchical, etc.) without any of the fluff or imposed structure layered on top. We've built a data storage component, a library to be incorporated into your application. And your product doesn't have to be a database. Most uses of Berkeley DB are within programs that never export storage services directly to their users, it can be a software application, a hardware controller, or a globally networked service.
Berkeley DB products are designed to let you focus on building your application while leaving the complexity of data storage to us.
For now DB->close().