FoundationDB
| Developer(s) | FoundationDB |
|---|---|
| Initial release | 4 March 2013 |
| Stable release | 2.0
/ 6 February 2014 |
| Repository | |
| Written in | C++ |
| Operating system | Cross-platform |
| Available in | English |
| Type | NoSQL |
| Website | www |
FoundationDB is a NoSQL database with a shared nothing architecture.[1] The product is designed around a "core" database, with additional features supplied in "layers."[2] The core database exposes an ordered key-value store with transactions.[3] The transactions are able to read or write multiple keys stored on any machine in the cluster while fully supporting ACID properties.[4] Transactions are used to implement a variety of data models via layers.
The FoundationDB Alpha program began in January 2012 and concluded on March 4, 2013 with their public Beta release.[5] Their 1.0 version was released for general availability on August 20, 2013. The latest stable version, 2.0, was released on February 6, 2014.
Main features
The main features of FoundationDB include the following:
- Ordered key-value store
- In addition to supporting standard key-based reads and writes, the ordering property enables range reads that can efficiently scan large swaths of data.[3]
- Transactions
- Transaction processing employs multiversion concurrency control for reads and optimistic concurrency for writes. Transactions can span multiple keys stored on multiple machines.
- ACID properties
- FoundationDB guarantees serializable isolation and strong durability via redundant storage on disk before transactions are considered committed.
- Layers
- Layers map new data models, APIs, and query languages to the FoundationDB core. They employ FoundationDB's ability to update multiple data elements in a single transaction, ensuring consistency.[2] An example is their SQL layer.[6]
- Commodity clusters
- FoundationDB is designed for deployment on distributed clusters of commodity hardware running Linux.[7]
- Replication
- FoundationDB stores each piece of data on multiple machines according to a configurable replication factor. Triple replication is the recommended mode for clusters of 5 or more machines.
- Scalability
- FoundationDB is designed to support horizontal scaling though the addition of machines to a cluster while automatically handling data replication and partitioning.
- Systems supported
- FoundationDB supports packages for Linux, Windows, and Mac OS X. The Linux version supports production clusters, while the Windows and Mac OS X versions support local operation for development purposes. Configurations on Amazon EC2 are also supported.[8]
- Programming language bindings
- FoundationDB supports language bindings for Python, Go, Ruby, Node.js, Java, PHP, and C, all of which are made available with the product.[8]
Design limitations
The design of FoundationDB results in several limitations:
- Long transactions
- FoundationDB does not support transactions running over five seconds.
- Large transactions
- Transaction size cannot exceed 10 MB of total written keys and values.
- Large keys and values
- Keys cannot exceed 10 kB in size. Values cannot exceed 100 kB in size.
History
FoundationDB, headquartered in Vienna, VA,[8] was started in 2009 by Nick Lavezzo, Dave Rosenthal, and Dave Scherer, drawing on their experience in executive and technology roles at their previous company, Visual Sciences.[9]
See also
References
- ^ Database House Wants You to Stop Dropping ACID
- ^ a b FoundationDB Releases Beta of its 'NoSQL/YesACID' Database
- ^ a b FoundationDB's ACID Compliant NoSQL Available
- ^ FoundationDB's NoSQL Breakthrough Challenges Relational Database Dominance
- ^ FoundationDB Brings Transactions to NoSQL
- ^ The FoundationDB SQL Layer
- ^ FoundationdB Releases New NoSQL Data Platform
- ^ a b c FoundationDB Aims to Consolidate NoSQL
- ^ SQL or NoSQL: FoundationDB Launches a 'Best of Both Worlds' Database