Go to file
Stephen Atherton aa8b4c52d5 Removed backup URL from trace events. 2017-12-21 18:22:14 -08:00
bindings updated documentation to reflect startNetwork starting a thread 2017-12-15 15:59:51 -08:00
build Patch up the makefiles and remove references to the completable bindings 2017-12-13 11:07:19 -08:00
design tuple and versionstamp documentation updates 2017-10-24 17:53:16 -07:00
fdbbackup Add datetime conversion error message in backup 2017-12-21 14:45:05 -08:00
fdbcli Better message is displayed to the user. 2017-11-09 13:55:19 -08:00
fdbclient Removed backup URL from trace events. 2017-12-21 18:22:14 -08:00
fdbmonitor Updates to fdbmonitor logging so that each line contains a timestamp, severity, logGroup, and process (e.g. fdbmonitor or fdbserver.4689, etc.). Remove usages of perror. 2017-10-31 11:07:06 -07:00
fdbrpc Whitespace normalization. 2017-12-21 12:07:29 -08:00
fdbserver Merge pull request #226 from cie/fix-taskBucket-unblockFuture 2017-12-20 18:00:54 -08:00
fdbservice Initial repository commit 2017-05-25 13:48:44 -07:00
flow Merge branch 'master' of github.com:apple/foundationdb 2017-12-21 01:58:47 -08:00
layers Remove a few more outdated items 2017-09-01 09:15:59 -07:00
packaging Merge branch 'release-5.0' 2017-11-02 10:42:30 -07:00
recipes Update API_VERSION from 500 to 510 2017-10-11 13:49:38 -07:00
tests Merge pull request #226 from cie/fix-taskBucket-unblockFuture 2017-12-20 18:00:54 -08: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 Patch up the makefiles and remove references to the completable bindings 2017-12-13 11:07:19 -08: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 Update versions.target 2017-11-02 10:29:34 -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.