org.foundationdb:fdb-java
Advanced tools
Java bindings for the FoundationDB database. These bindings require the FoundationDB client, which is under a different license. The client can be obtained from https://github.com/apple/foundationdb/releases
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.
The lastest stable releases are (were) versions that are recommended for production use, which have been extensively validated via simulation and real cluster tests and used in our production environment.
| Branch | Latest Production Release | Notes |
|---|---|---|
| 7.3 | 7.3.43 | Supported |
| 7.2 | Experimental | |
| 7.1 | 7.1.57 | Bug fixes |
| 7.0 | Experimental | |
| 6.3 | 6.3.25 | Unsupported |
Supported branches are those we actively maintain and will publish new patch releases.Bug fixes are branches we still accept bug fixes into the branch, but may not publish newer patch releases. The community can build the latest release binaries if needed and is encouraged to upgrade to the Supported branches.Experimental branches are those used for internal feature testing. They are not recommended for production use.Unsupported branches are those which will no longer receive any updates.If you are running on old production releases, we recommend always upgrading to the next major release's latest version, and then continue to the next major version, e.g., 6.2.X -> 6.3.25 -> 7.1.57 -> 7.3.43. These upgrade paths have been well tested in production (skipping a major release, not marked as Experimental, for an upgrade is only tested in simulation).
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 foundationdb/build, which has all dependencies installed. The Docker image definitions used by FoundationDB team members can be found in the dedicated repository.
To build outside of the official docker image, you'll need at least these dependencies:
If compiling for local development, please set -DUSE_WERROR=ON in
cmake. Our CI compiles with -Werror 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:
cd <PATH_TO_BUILD_DIRECTORY>cmake -G Ninja <PATH_TO_FOUNDATIONDB_DIRECTORY>ninja # If this crashes it probably ran out of memory. Try ninja -j1The language bindings that are supported by cmake will have a corresponding
README.md file in the corresponding bindings/lang directory.
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.
compile_commands.jsonCMake 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 compile_commands.json file in the source
directory. This can than be used for tools like
CCLS,
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 compile_commands.json, you must pass
-DCMAKE_EXPORT_COMPILE_COMMANDS=ON. This also enables the target
processed_compile_commands, which rewrites compile_commands.json 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 foundationdb/build docker
image, the resulting paths will still be incorrect and require manual fixing.
One will wish to re-run cmake with -DCMAKE_EXPORT_COMPILE_COMMANDS=OFF 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 OPEN_FOR_IDE 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 an Xcode project with the following command:
cmake -G Xcode -DOPEN_FOR_IDE=ON <FDB_SOURCE_DIRECTORY>
You should create a second build-directory which you will use for building and debugging.
Check out this repo on your server.
Install compile-time dependencies from ports.
(Optional) Use tmpfs & ccache for significantly faster repeat builds
(Optional) Install a JDK for Java Bindings. FoundationDB currently builds with Java 8.
Navigate to the directory where you checked out the foundationdb repo.
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 \
-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
foundationdb/build 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
For RPM simply replace DEB with RPM.
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>
To generate a installable package,
ninja
$SRCDIR/packaging/osx/buildpkg.sh . $SRCDIR
Under Windows, only Visual Studio with ClangCl is supported
-DBOOST_ROOT=<PATH_TO_BOOST> with cmake if unpacked elsewheremkdir build && cd buildcmake -G "Visual Studio 16 2019" -A x64 -T ClangCl <PATH_TO_FOUNDATIONDB_SOURCE>msbuild /p:Configuration=Release foundationdb.sln/p:UseMultiToolTask=true and /p:CL_MPCount=<NUMBER_OF_PARALLEL_JOBS>FAQs
Java bindings for the FoundationDB database. These bindings require the FoundationDB client, which is under a different license. The client can be obtained from https://github.com/apple/foundationdb/releases
We found that org.foundationdb:fdb-java demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.