TigerBeetle is a distributed financial accounting database designed for mission critical safety and performance.
First, get TigerBeetle running:
- Run a single-node cluster with a single binary
- Or run a single-node cluster with Docker
- Or run a three-node cluster with docker-compose
Then, try creating accounts and transfers using Node.js as a CLI.
Designing for TigerBeetle
When integrating TigerBeetle into your project, consider the following:
- TigerBeetle and consistency
- Modeling application data within TigerBeetle
- How two-phase transfers work
- How client sessions work
- How client requests work
Here are some common use-cases for TigerBeetle:
We officially support the following libraries for communicating with a TigerBeetle cluster:
Within each client library README you will find links to sample code.
To understand TigerBeetle's data model, see:
- Watch our talks, listen to our podcasts
- Read HISTORY.md
- Read DESIGN.md
- Read DEEP_DIVE.md
- Read TIGER_STYLE.md
- Read HACKING.md
- And explore internal READMEs within the TigerBeetle src directory