awesome-repositories.com
Blog
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
tigerbeetle avatar

tigerbeetle/tigerbeetle

0
View on GitHub↗
16,291 estrellas·841 forks·Zig·Apache-2.0·8 vistastigerbeetle.com↗

Tigerbeetle

TigerBeetle is a distributed financial accounting database designed for high-volume transaction processing. It functions as a specialized transaction engine that enforces strict double-entry bookkeeping invariants, ensuring that every debit and credit is balanced and accounted for with absolute consistency. By utilizing a consensus-based replication model, the system provides high availability and data durability across geographically distributed clusters, making it suitable for mission-critical financial infrastructure.

The system distinguishes itself through a performance-oriented architecture that prioritizes deterministic execution and low latency. It employs a single-threaded state machine to eliminate lock contention and uses static memory allocation to avoid garbage collection pauses. To maintain integrity, it records all operations in an immutable, append-only audit log and uses 128-bit integers for currency to ensure precise arithmetic. The engine supports complex financial workflows, including atomic currency exchanges and two-phase commit protocols, which allow for the reservation and settlement of funds without risking data inconsistencies.

Beyond its core processing capabilities, the platform includes robust operational primitives for managing the full lifecycle of financial data. It provides native language drivers for client integration, supports real-time ledger data streaming for external auditing, and offers tools for monitoring performance metrics and request latency. The system is designed for resilience, featuring automated failover, replica recovery, and rolling upgrade procedures that allow for continuous operation even during hardware or network failures.

The project provides comprehensive documentation and native client libraries to facilitate integration into existing financial systems. It is configured to run on high-performance storage infrastructure, including local NVMe drives and raw block devices, to maximize throughput.

Features

  • Distributed Ledgers - A high-performance, fault-tolerant database designed for mission-critical double-entry bookkeeping.
  • Ledger Engines - Builds high-performance, double-entry accounting systems that require strict transactional integrity.
  • High-Volume - Executes millions of financial operations per second with low latency by utilizing optimized, lock-free concurrency.
  • Accounting Engines - Enforces balance invariants, atomic transfers, and idempotent operations for complex financial workflows.

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI
  • Accounting Invariants - TigerBeetle validates debit and credit balances within the database to ensure funds are always accounted for and balance limits are respected.
  • Transaction Processors - Optimized for millions of financial ledger entries per second using a single-core architecture.
  • Financial Transaction Processing - Executes immutable ledger entries that debit one account and credit another, supporting both single-phase and two-phase transactions.
  • High Availability Architectures - Maintains continuous operation through automated consensus-based failover and multi-cloud replication.
  • Balance Tracking - Maintains running totals of debits and credits for accounts to allow applications to compute balances.
  • Persistence & Durability - Replicates data across multiple nodes using a consensus protocol to ensure records survive hardware or network failures.
  • Distributed Databases - Provides a consensus-based storage engine that ensures strict serializability, data durability, and high availability.
  • Strict Serializability - Processes all transactions sequentially through a single state machine to ensure absolute consistency.
  • Two-Phase Commit - Reserves funds in a pending state and resolves them via posting, voiding, or expiration to support complex financial workflows.
  • High Availability Clusters - Runs a cluster of replicas to provide high-availability and data safety for financial transactions across multiple nodes.
  • Raft Consensus Implementations - Coordinates multiple server replicas using the Raft protocol to ensure strict serializability and high availability.
  • Integer-Based Currency - Uses 128-bit integers to represent currency units, ensuring precise calculations by avoiding floating-point arithmetic.
  • Immutable - Records all transactions as append-only entries that cannot be erased or modified, ensuring a permanent and auditable history.
  • Account Management - Registers and tracks financial accounts, supporting custom metadata and batch operations to maintain accurate balances.
  • Append-Only Storage Engines - Persists all financial transactions as an immutable, checksummed, and hash-chained append-only log for auditability.
  • Backup and Recovery - Detects and repairs data file corruption across replicas while enforcing safe shutdown protocols.
  • Clock Synchronization Protocols - Aggregates physical clock readings from multiple replicas to maintain a consistent wall-clock time across the distributed system.
  • Currency Conversion - Links multiple ledger transfers into a single atomic unit to ensure currency conversion occurs as an indivisible transaction.
  • Atomic Transfer Chains - Links multiple individual transfers into a single atomic unit to ensure complex sequences of financial events succeed or fail together.
  • Replica Recovery - Restores cluster integrity by re-synchronizing data to a replacement node after a permanent hardware or instance failure.
  • Atomic Chains - Links multiple ledger events into a single atomic chain that succeeds or fails as a unit.
  • Distributed Database Clusters - Deploys and manages high-availability database clusters that ensure data durability and consistency across multiple geographic nodes.
  • Multi-Region Deployment Strategies - Deploys cluster nodes across multiple sites to maintain transaction processing capabilities during site failures.
  • Rate Limiting - Restricts the frequency of transactions for specific accounts or entities to protect system throughput and prevent resource exhaustion.
  • Ledger Querying - Filters account transfers and historical balances based on specified parameters to retrieve precise financial records.
  • System Timestamping - Generates unique, immutable, and totally ordered timestamps for all records upon ingestion.
  • Commit Protocols - Implements two-phase commit protocols to reserve funds in a pending state before final settlement for atomic financial operations.
  • Operation Idempotency - Uses unique identifiers for accounts and transfers to prevent duplicate processing during retries or system failures.
  • Accounting Systems - Distributed financial accounting database for high-performance transaction integrity.
  • Herramientas de desarrollo - Financial transactions database.
  • Distributed System Components - Distributed financial database designed with simulation-first principles.
  • Balance History - Maintains a chronological record of account balances over time for auditing and reporting purposes.
  • Fault Domain Isolation - Enforces the use of independent hardware and network infrastructure for each replica to prevent correlated failures.
  • Real-Time Data Streaming - Exports transaction logs and state changes to external systems in real-time for auditing and analytical tasks.
  • Sequential Execution Engines - Processes all transactions sequentially on a single core to eliminate lock contention and ensure absolute consistency.
  • Zero-Copy Mechanisms - Transfers data directly between network buffers and application memory to minimize CPU overhead and maximize transaction throughput.
  • Correction Mechanisms - Reverses or adjusts previously committed transactions by issuing compensating entries that maintain ledger history integrity.
  • Metrics Exporters - Streams internal performance and status data to external collection agents using standard protocols for real-time observability.
  • System Audit Trails - Records immutable, append-only logs of all financial events to provide a verifiable and permanent history.
  • Metadata Storage - Provides indexed fields for arbitrary application data to support querying and entity linking for financial accounts.
  • Database Drivers - Provides native language drivers to ensure seamless communication with the storage layer and database operations.
  • Cluster Upgrades - Updates the database cluster by replacing binaries across replicas without requiring downtime.
  • Request Batching - Combines multiple operations into single network calls to increase data throughput and reduce response latency.
  • Static Allocation Strategies - Pre-allocates all required memory at startup to avoid runtime garbage collection pauses and ensure predictable performance.
  • Expiration Logic - Automatically releases reserved funds back to original accounts if a transaction is not settled within a predefined time interval.
  • Latency Monitoring - Records the duration of specific transaction operations to help evaluate performance and identify bottlenecks within the database engine.
  • Fee Recording - Appends a distinct transfer to an exchange chain to capture the spread as a transparent, auditable fee.
  • Cache Efficiency Analysis - Exposes hit and miss counts to determine if memory allocation for data caching is appropriately sized for the current workload.
  • Compatibility Migrators - Ensures that ledger data files created by older versions remain readable and functional after software upgrades.
  • Timestamping Mechanisms - Generates unique and totally ordered timestamps for all records upon ingestion to ensure consistent temporal ordering.
  • Storage Configurations - Optimizes data persistence by supporting local NVMe drives, raw block devices, and remote block storage configurations.
  • Client Session Management - Registers unique client identifiers with the cluster to establish request sequences and enforce concurrency limits.
  • Memory Locking - Prevents the operating system from swapping active memory to disk by configuring system limits to maintain consistent performance.
  • Request Lifecycle Control - Controls the execution of database operations through client-side cancellation and connection management for long-running tasks.

    • Historial de estrellas

    Gráfico del historial de estrellas de tigerbeetle/tigerbeetleGráfico del historial de estrellas de tigerbeetle/tigerbeetle

    Preguntas frecuentes

    ¿Qué hace tigerbeetle/tigerbeetle?

    TigerBeetle is a distributed financial accounting database designed for high-volume transaction processing. It functions as a specialized transaction engine that enforces strict double-entry bookkeeping invariants, ensuring that every debit and credit is balanced and accounted for with absolute consistency. By utilizing a consensus-based replication model, the system provides high availability and data durability across geographically distributed clusters, making it…

    ¿Cuáles son las características principales de tigerbeetle/tigerbeetle?

    Las características principales de tigerbeetle/tigerbeetle son: Distributed Ledgers, Ledger Engines, High-Volume, Accounting Engines, Accounting Invariants, Transaction Processors, Financial Transaction Processing, High Availability Architectures.

    ¿Qué alternativas de código abierto existen para tigerbeetle/tigerbeetle?

    Las alternativas de código abierto para tigerbeetle/tigerbeetle incluyen: redis/go-redis — This project is a feature-rich Go client library designed for interacting with Redis. It serves as a comprehensive… yugabyte/yugabyte-db — YugabyteDB is a distributed SQL database and relational data store designed for horizontal scalability and high… akaunting/akaunting — Akaunting is a modular business enterprise resource planning system and self-hosted accounting software. It provides a… tikv/tikv — TiKV is a distributed transactional key-value store designed for horizontal scalability and high availability. It… beancount/beancount — Beancount is a plain-text double-entry accounting system. It enforces zero-sum transactions, organizes accounts into a… hashicorp/nomad — Nomad is a distributed workload orchestrator and infrastructure automation platform designed to manage the lifecycle…

    Alternativas open-source a Tigerbeetle

    Proyectos open-source similares, clasificados según cuántas características comparten con Tigerbeetle.
    • redis/go-redisAvatar de redis

      redis/go-redis

      22,159Ver en GitHub↗

      This project is a feature-rich Go client library designed for interacting with Redis. It serves as a comprehensive interface for managing remote data stores, enabling developers to execute standard database commands, handle complex data structures, and perform asynchronous operations within Go applications. The library distinguishes itself through its support for advanced Redis capabilities, including connection pooling, pipelining, and transactional integrity. It provides specialized primitives for managing distributed clusters, including automated topology updates and request routing to sha

      Gogogolangredis
      Ver en GitHub↗22,159
    • yugabyte/yugabyte-dbAvatar de yugabyte

      yugabyte/yugabyte-db

      10,349Ver en GitHub↗

      YugabyteDB is a distributed SQL database and relational data store designed for horizontal scalability and high availability across multiple nodes or regions. It functions as a cloud-native system that ensures continuous availability and supports PostgreSQL compatible query languages and drivers. The system includes specialized capabilities as a vector database for AI, utilizing high-dimensional indexing to perform similarity searches. It is engineered as a multi-region cloud database that synchronizes data across different geographic locations to maintain global availability. The project co

      Ccloud-nativecppdatabase
      Ver en GitHub↗10,349
    • akaunting/akauntingAvatar de akaunting

      akaunting/akaunting

      9,604Ver en GitHub↗

      Akaunting is a modular business enterprise resource planning system and self-hosted accounting software. It provides a comprehensive platform for small business financial management, centering on a double-entry bookkeeping system with a general ledger and chart of accounts. The platform is designed for extensibility through a module-based architecture and a dedicated marketplace for procuring third-party applications. It supports multi-tenant data isolation and utilizes role-based access control to manage granular user permissions. Its capability surface covers a wide range of business opera

      PHPaccountingakauntingbalance
      Ver en GitHub↗9,604
    • tikv/tikvAvatar de tikv

      tikv/tikv

      16,535Ver en GitHub↗

      TiKV is a distributed transactional key-value store designed for horizontal scalability and high availability. It functions as a storage engine that maintains massive datasets across a cluster of physical nodes, ensuring that information remains accessible and consistent even when individual hardware components fail. The system utilizes a consensus-based replication model to synchronize data across nodes, ensuring that all replicas agree on the order of operations. It manages data distribution through a sharding mechanism that partitions large datasets into smaller groups, each governed by in

      Rustcncfconsensusdistributed-transactions
      Ver en GitHub↗16,535
    Ver las 30 alternativas a Tigerbeetle→