A layer can provide a new data model, compatibility with existing systems, or even serve as an entire framework. Multiple layers can be used at the same time, enabling a single FoundationDB database to consolidate multiple data stores. Read the Layer White Paper →
If you're interested in building your own layer, make sure to check out the examples in Design Recipes.
Have you built a layer on top of FoundationDB that you'd like to include on this page? Let us know!Submit a Layer
These layers are ready for you to use today. Some are examples of how to build a layer to provide a certain utility, data model, etc.
Protocol Buffers Layer for Ruby
Document Model and Query Layer for NodeJS
Implements the Blueprints 2.3.0 graph API. Allows FoundationDB to be used as a storage layer for the Tinkerpop stack. Supports all required and most optional Blueprints features, including transactions over the graph database.
Storage backend for Titan, a transactional, scalable graph database produced by Aurelius. Builds on our Blueprints layer and employs Titan's TinkerPop integration.
A FoundationDB broker and backend for Celery, an asynchronous task queue/job queue based on distributed message passing.
These layers are still being built out, so don't count on using them for anything real yet.
Store your Ruby application data in various data models, including Document and Key-Value.
A full SQL implementation on top of FoundationDB. It provides the same high performance, multi-node scalability, fault-tolerance, and true multi-key ACID transactions.
Distributed coordination service supporting locking, leader election, and service discovery. Inspired by ZooKeeper but higher level. Provides DNS and REST APIs.
This layer provides two integration points with Lucene, FDBDirectory and FDBCodec. These are full implementations of the Directory and Codec interfaces.