FoundationDB - the open source, distributed, transactional key-value store
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
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 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.
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 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.
Developers interested in using FoundationDB can get started by downloading and installing a binary package. Please see the downloads page for a list of available packages.
Developers on an 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.
The official docker image for building is
. It has all dependencies installed. To build outside the official docker image you'll need at least these dependencies:
If compiling for local development, please set
in cmake. Our CI compiles with
on, so this way you'll find out about compiler warnings that break the build earlier.
Once you have your dependencies, you can run cmake and then build:
cmake -G Ninja <path_to_foundationdb_directory></path_to_foundationdb_directory>
ninja # If this crashes it probably ran out of memory. Try ninja -j1
The language bindings that are supported by cmake will have a corresponding
file in the corresponding
Generally, cmake will build all language bindings for which it can find all necessary dependencies. After each successful cmake run, cmake will tell you which language bindings it is going to build.
CMake can build a compilation database for you. However, the default generated one is not too useful as it operates on the generated files. When running make, the build system will create another
file in the source directory. This can than be used for tools likeCCLS,CQuery, etc. This way you can get code-completion and code navigation in flow. It is not yet perfect (it will show a few errors) but we are constantly working on improving the development experience.
CMake will not produce a
, you must pass
. This also enables the target
, which rewrites
to describe the actor compiler source file, not the post-processed output files, and places the output file in the source directory. This file should then be picked up automatically by any tooling.
Note that if building inside of the
docker image, the resulting paths will still be incorrect and require manual fixing. One will wish to re-run
to prevent it from reverting the manual changes.
CMake has built in support for a number of popular IDEs. However, because flow files are precompiled with the actor compiler, an IDE will not be very useful as a user will only be presented with the generated code - which is not what she wants to edit and get IDE features for.
The good news is, that it is possible to generate project files for editing flow with a supported IDE. There is a CMake option called
which will generate a project which can be opened in an IDE for editing. You won't be able to build this project, but you will be able to edit the files and get most edit and navigation features your IDE supports.
For example, if you want to use XCode to make changes to FoundationDB you can create a XCode-project with the following command:
cmake -G Xcode -DOPEN\_FOR\_IDE=ON <fdb_source_directory> </fdb_source_directory>
You should create a second build-directory which you will use for building and debugging.
Build from source.
sudo pkg install -r FreeBSD \ shells/bash devel/cmake devel/ninja devel/ccache \ lang/mono lang/python3 \ devel/boost-libs devel/libeio \ security/openssl mkdir .build && cd .build cmake -G Ninja \ -DUSE\_CCACHE=on \ -DDISABLE\_TLS=off \ -DUSE\_DTRACE=off \ .. ninja -j 10 # run fast tests ctest -L fast # run all tests ctest --output-on-failure -v
There are no special requirements for Linux. A docker image can be pulled from
that has all of FoundationDB's dependencies pre-installed, and is what the CI uses to build and test PRs.
cmake -G Ninja <fdb_source_dir> ninja cpack -G DEB </fdb_source_dir>
For RPM simply replace
The build under MacOS will work the same way as on Linux. To get boost and ninja you can use Homebrew.
cmake -G Ninja <path_to_foundationdb_source> </path_to_foundationdb_source>
To generate a installable package, you can use cpack:
ninja cpack -G productbuild
Under Windows, the build instructions are very similar, with the main difference that Visual Studio is used to compile.
to the unpacked location and JAVA_COMPILE to
cmake -G "Visual Studio 15 2017 Win64" -DBOOST\_ROOT=<path_to_boost> <path_to_foundationdb_directory></path_to_foundationdb_directory></path_to_boost>
. You can also open the resulting solution in Visual Studio and compile from there. However, be aware that using Visual Studio for development is currently not supported as Visual Studio will only know about the generated files.
msbuild /p:Configuration=Release foundationdb.sln
is located at
for Visual Studio 15.
c:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
If you installed WIX before running
you should find the
in your build directory under
TODO: Re-add instructions for TLS support #3022