Go to file
Stephen Atherton 42955012e9 Merge branch 'release-5.0'
# Conflicts:
#	fdbrpc/BlobStore.actor.cpp
#	flow/error_definitions.h
2017-10-20 21:16:55 -07:00
bindings changed java package from com.apple.cie.foundationdb to com.apple.foundationdb 2017-10-16 08:31:44 -07:00
build Initial repository commit 2017-05-25 13:48:44 -07:00
design Update tuple.md 2017-09-19 22:41:55 +00:00
fdbbackup Fixing windows build. Fixing backup.actor.cpp 2017-10-13 17:41:17 -07:00
fdbcli Address review comments. 2017-10-16 16:46:52 -07:00
fdbclient Merge branch 'release-5.0' 2017-10-20 21:16:55 -07:00
fdbmonitor Add support for retrying a process if fork fails. The HUP signal now causes configuration to be reloaded and timeouts to be reset. A little refactoring to make this easier. 2017-10-05 08:23:52 -07:00
fdbrpc Merge branch 'release-5.0' 2017-10-20 21:16:55 -07:00
fdbserver Fail with correct error code in case of abort or discontinue of 2017-10-18 23:17:48 -07:00
fdbservice Initial repository commit 2017-05-25 13:48:44 -07:00
flow Merge branch 'release-5.0' 2017-10-20 21:16:55 -07:00
layers Remove a few more outdated items 2017-09-01 09:15:59 -07:00
packaging Merge branch 'release-5.0' 2017-10-20 21:16:55 -07:00
recipes updated paths and formatting with go docs and examples 2017-07-05 17:25:32 -07:00
tests Fixing code review comments. 2017-09-29 15:58:36 -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 Replace backtrace with absl::GetStackTrace on non-MacOS platforms. 2017-10-16 16:05:02 -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 reverting versions.target after docs build to 5.0.2 2017-07-13 10:28:16 -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.