Go to file
Vishesh Yadav 43e5a46f9b Change Endpoint::address(NetworkAddress) to vector<NetworkAddress>
Extend `Endpoint` class to take multiple NetworkAddresses instead of
just one. Hence, to talk to an endpoint instead of one IP:PORT, we'll
have multiple IP:PORT pairs.

This patch simply adds the field and makes changes to compile the
codebase. The first element of of `address` field is used everywhere.
Hence the way we talk to remains same with this patch.

NOTE:

Directly accessing the first memeber of Endpoint::address is unsafe
as Endpoint() doesn't enforces non-empty address list. However, since
the correctness test pass for now and are anyway replacing all those
unsafe accesses with ones considering the whole vector, this patch
ignores to access them in safe way.
2018-12-13 13:36:52 -08:00
FDBLibTLS Merge branch 'release-6.0' 2018-11-10 13:04:24 -08:00
bindings Remove unused localAddress parameter from newNet2 and Net2 classes 2018-12-13 13:36:52 -08:00
build Merge branch 'release-6.0' 2018-11-13 16:06:39 -08:00
design Update backup.md 2018-10-29 14:11:20 -07:00
documentation Make polling_loop yield agree with usage in docs 2018-12-11 14:41:49 -08:00
fdbbackup Merge branch 'release-6.0' 2018-11-10 13:04:24 -08:00
fdbcli Merge branch 'release-6.0' 2018-12-03 18:26:52 -08:00
fdbclient Change Endpoint::address(NetworkAddress) to vector<NetworkAddress> 2018-12-13 13:36:52 -08:00
fdbmonitor Merge branch 'release-6.0' 2018-11-12 20:26:58 -08:00
fdbrpc Change Endpoint::address(NetworkAddress) to vector<NetworkAddress> 2018-12-13 13:36:52 -08:00
fdbserver Change Endpoint::address(NetworkAddress) to vector<NetworkAddress> 2018-12-13 13:36:52 -08:00
fdbservice Fix typo: orginal > original 2018-04-20 17:29:13 +09:00
flow Change Endpoint::address(NetworkAddress) to vector<NetworkAddress> 2018-12-13 13:36:52 -08: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 branch 'release-6.0' 2018-12-03 18:26:52 -08:00
recipes tuple.Tuple needed to be deconstructed into TupleElement items before appending to key tuple 2018-10-23 22:13:52 -05:00
tests TeamCollection: Improve code efficiency 2018-12-12 22:38:38 -08:00
.clang-format Add a clang-format config file. 2018-03-29 12:10:12 -07:00
.gitignore Add creating compile_commands.json to the build system. 2018-08-14 15:50:26 -07: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 Merge pull request #774 from apple/release-6.0 2018-09-18 15:01:26 -07:00
README.md Update README.md (#946) 2018-11-27 15:16:43 -08:00
foundationdb.sln removed references to nodejs bindings 2018-04-06 17:17:45 -07:00
versions.target update versions target to 6.0.18 2018-12-03 18:21:35 -08: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.

    cd /dir/path/foundationdb
    docker build ./build -t <image-tag-name>
    
  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' <image-tag-name> /bin/bash
    
  5. Navigate to the container's mounted directory which contains 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.