Go to file
Evan Tschannen 8a24bf6124 describe did not list all the log sets 2018-06-10 12:38:50 -07:00
FDBLibTLS Merge release-5.2 into master 2018-05-23 15:32:56 -07:00
bindings Merge pull request #395 from dkoston/go-client-readme-add-mono 2018-05-29 10:22:25 -07:00
build Merge pull request #307 from nbraud/scver.mk 2018-05-09 21:05:11 -07:00
design Backup design documentation. 2018-02-22 18:09:41 -08:00
documentation Merge release-5.2 into master 2018-05-23 15:32:56 -07:00
fdbbackup remove trailing whitespace from our copyright headers ; fixed formatting of python setup.py 2018-02-21 10:25:11 -08:00
fdbcli Merge release-5.2 into master 2018-05-23 15:32:56 -07:00
fdbclient fix: do not finish a shard relocation until all of the storage servers have made the current recovery version durable. This is to prevent dropping a needed storage server as a source for a shard after dropping a remote configuration 2018-06-07 12:29:25 -07:00
fdbmonitor fix fdbmonitor help message output ; fix spelling error Ratekeeper.actor.cpp 2018-05-07 16:19:50 -07:00
fdbrpc fix: we cannot kill all of the remote tlogs, because we still need their data to copy to the next generation in the same data center 2018-06-08 15:28:44 -07:00
fdbserver describe did not list all the log sets 2018-06-10 12:38:50 -07:00
fdbservice Fix typo: orginal > original 2018-04-20 09:27:19 -07:00
flow fix: we must server getTeam requests before readyToStart is set because we cannot complete relocateShard requests without getTeam responses from both team collections 2018-06-07 16:14:40 -07:00
layers remove trailing whitespace from our copyright headers ; fixed formatting of python setup.py 2018-02-21 10:25:11 -08:00
packaging Merge release-5.2 into master 2018-05-23 15:32:56 -07:00
recipes bump API version to 520 2018-03-02 10:30:41 -08:00
tests Merge pull request #297 from apple/release-5.2 2018-05-08 12:04:20 -07:00
.clang-format Add a clang-format config file. 2018-03-29 12:10:12 -07:00
.gitignore Exclude .vs folder (Visual Studio 2017) 2018-05-12 15:20:52 +02:00
ACKNOWLEDGEMENTS Initial repository commit 2017-05-25 13:48:44 -07:00
CODE_OF_CONDUCT.md Updates markdown link to Contributor Covenant homepage in the Code of Conduct. 2018-04-18 01:08:55 -04:00
CONTRIBUTING.md Adds initial draft of contribution guide. 2018-04-12 17:59:32 -07:00
LICENSE Initial repository commit 2017-05-25 13:48:44 -07:00
Makefile Use mcs instead of dmcs when dmcs is not available 2018-05-07 15:16:22 -07:00
README.md Update Linux compilation instructions 2018-04-23 14:43:09 +01:00
foundationdb.sln removed references to nodejs bindings 2018-04-06 17:17:45 -07:00
versions.target updated versions.target for 5.1.8 2018-04-18 20:40:36 -07:00

README.md

FoundationDB logo

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.

To learn more about FoundationDB, visit foundationdb.org

Documentation

Documentation can be found online at https://apple.github.io/foundationdb/. The documentation covers details of API usage, background information on design philosophy, and extensive usage examples. Docs are built from the source in this repo.

Forums

The FoundationDB Forums are the home for most of the discussion and communication about the FoundationDB project. We welcome your participation! We want FoundationDB to be a great project to be a part of and, as part of that, have established a Code of Conduct to establish what constitutes permissible modes of interaction.

Contributing

Contributing to FoundationDB can be in contributions to the code base, sharing your experience and insights in the community on the Forums, or contributing to projects that make use of FoundationDB. Please see the contributing guide for more specifics.

Getting Started

Binary downloads

Developers interested in using the FoundationDB store for an application can get started easily by downloading and installing a binary package. Please see the downloads page for a list of available packages.

Compiling from source

Developers on a OS for which there is no binary package, or who would like to start hacking on the code can get started by compiling from source.

macOS

  1. Check out this repo on your Mac.
  2. Install the Xcode command-line tools.
  3. Download version 1.52 of Boost.
  4. Set the BOOSTDIR environment variable to the location containing this boost installation.
  5. Install Mono.
  6. Install a JDK. FoundationDB currently builds with Java 8.
  7. Navigate to the directory where you checked out the foundationdb repo.
  8. Run make.

Linux

  1. Install Docker.
  2. Check out the foundationdb repo.
  3. Build Linux docker image using the file Dockerfile located in the build source directory.
  4. Run the docker image interactively Docker Run with the directory containing the foundationdb repo mounted Docker Mounts. docker run -it -v '/local/dir/path/foundationdb:/docker/dir/path/foundationdb' /bin/bash
  5. Navigate to the mounted directory containing the foundationdb repo. cd /docker/dir/path/foundationdb
  6. Run make.

This will build the fdbserver binary and the python bindings. If you want to build our other bindings, you will need to install a runtime for the language whose binding you want to build. Each binding has an .mk file which provides specific targets for that binding.