TigerBeetle in Your System Architecture
TigerBeetle is an Online Transaction Processing (OLTP) database built for safety and performance. It is not a general purpose database like PostgreSQL or MySQL. Instead, TigerBeetle works alongside your general purpose database, which we refer to as an Online General Purpose (OLGP) database.
TigerBeetle should be used in the data plane, or hot path of transaction processing, while your general purpose database is used in the control plane and may be used for storing information or metadata that is updated less frequently.
Division of Responsibilities
App or Website
- Initiate transactions
- Generate Transfer and Account IDs
Stateless API Service
- Handle authentication and authorization
- Create account records in both the general purpose database and TigerBeetle when users sign up
- Cache ledger metadata
- Batch transfers
- Apply exchange rates for currency exchange transactions
General Purpose (OLGP) Database
- Store metadata about ledgers and accounts (such as string names or descriptions)
- Store mappings between integer type identifiers used in TigerBeetle and string representations used by the app and API
TigerBeetle (OLTP) Database
- Record transfers between accounts
- Track balances for accounts
- Enforce balance limits
- Enforce financial consistency through double-entry bookkeeping
- Enforce strict serializability of events
- Optionally store pointers to records or entities in the general purpose database in the
user_datafields
Ledger, Account, and Transfer Types
For performance reasons, TigerBeetle stores the ledger, account, and transfer types as simple integers. Most likely, you will want these integers to map to enums of type names or strings, along with other associated metadata.
The mapping from the string representation of these types to the integers used within TigerBeetle may be hard-coded into your application logic or stored in a general purpose (OLGP) database and cached by your application. (These mappings should be immutable and append-only, so there is no concern about cache invalidation.)
⚠️ Importantly, initiating a transfer should not require fetching metadata from the general purpose database. If it does, that database will become the bottleneck and will negate the performance gains from using TigerBeetle.
Specifically, the types of information that fit into this category include:
| Hard-coded in app or cached | In TigerBeetle |
|---|---|
| Currency or asset code's string representation (for example, "USD") | ledger and asset scale |
| Account type's string representation (for example, "cash") | code |
| Transfer type's string representation (for example, "refund") | code |
Authentication
TigerBeetle does not support authentication. You should never allow untrusted users or services to interact with it directly.
Also, untrusted processes must not be able to access or modify TigerBeetle's on-disk data file.