Go to file
Stephen Atherton 5049421a0e More comments, debug output improvements. 2017-08-28 17:26:53 -07:00
bindings Add back a cast that I shouldn’t have removed. 2017-05-26 15:20:47 -07:00
build Initial repository commit 2017-05-25 13:48:44 -07:00
fdbbackup Initial repository commit 2017-05-25 13:48:44 -07:00
fdbcli Fixed printf field width specifier to reduce compilation warnings within OS X 2017-05-26 14:51:34 -07:00
fdbclient Merge branch 'release-4.6' into release-5.0 2017-05-31 16:23:37 -07:00
fdbmonitor Initial repository commit 2017-05-25 13:48:44 -07:00
fdbrpc Merge branch 'release-5.0' 2017-05-31 17:10:48 -07:00
fdbserver More comments, debug output improvements. 2017-08-28 17:26:53 -07:00
fdbservice Initial repository commit 2017-05-25 13:48:44 -07:00
flow Merge branch 'master' into feature-redwood 2017-06-09 14:56:41 -07:00
layers Initial repository commit 2017-05-25 13:48:44 -07:00
packaging Initial repository commit 2017-05-25 13:48:44 -07:00
recipes Initial repository commit 2017-05-25 13:48:44 -07:00
tests Added use of IndirectShadowPager. Moved MemoryPager code into .cpp because of type conflicts and its implementation doesn’t need to be externally visible anyway. Added start of a performance test. Renamed tests. Correctness/set now has random reopen of disk based pager before verification. Added asserts for when keys or values that are too large to fit in a single page. 2017-07-13 22:11:48 -07:00
.gitignore Initial repository commit 2017-05-25 13:48:44 -07:00
ACKNOWLEDGEMENTS Initial repository commit 2017-05-25 13:48:44 -07:00
LICENSE Initial repository commit 2017-05-25 13:48:44 -07:00
Makefile Initial repository commit 2017-05-25 13:48:44 -07:00
README.md Initial repository commit 2017-05-25 13:48:44 -07:00
foundationdb.sln Initial repository commit 2017-05-25 13:48:44 -07:00
versions.target updated version.target to 5.1 2017-05-25 13:55:36 -07:00

README.md

FoundationDB

FoundationDB is a distributed database designed to handle large volumes of structured data across clusters of commodity servers. It organizes data as an ordered key-value store and employs ACID transactions for all operations. It is especially well-suited for read/write workloads but also has excellent performance for write-intensive workloads. Users interact with the database using API language binding.