awesome-repositories.com
Blog
MCP
awesome-repositories.com

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

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoServidor MCPAcerca deCómo clasificamosPrensa
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

7 repositorios

Awesome GitHub RepositoriesZero-Allocation Architectures

Software designs that eliminate temporary object creation to prevent garbage collection overhead.

Distinct from Incremental Garbage Collection: Neither GC tuning nor incremental GC describes the proactive architecture of avoiding allocations entirely.

Explore 7 awesome GitHub repositories matching software engineering & architecture · Zero-Allocation Architectures. Refine with filters or upvote what's useful.

Awesome Zero-Allocation Architectures GitHub Repositories

Encuentra los mejores repositorios con IA.Buscaremos los repositorios que mejor coincidan usando IA.
  • gunnarmorling/1brcAvatar de gunnarmorling

    gunnarmorling/1brc

    8,062Ver en GitHub↗

    The 1BRC (One Billion Row Challenge) is a Java performance benchmarking exercise that processes one billion temperature records from a text file to compute the minimum, mean, and maximum temperature per weather station. At its core, it is a large-scale data aggregation challenge designed to test how efficiently a Java program can parse and aggregate structured data from a plain text file, serving as both a programming exercise and a benchmark for Java performance optimization. The project distinguishes itself through a collection of performance-oriented architectural patterns for high-through

    Pre-allocates all working data structures upfront and avoids object creation during the hot loop to eliminate GC pauses.

    Java1brcchallenges
    Ver en GitHub↗8,062
  • mikaelemmmm/go-zero-looklookAvatar de Mikaelemmmm

    Mikaelemmmm/go-zero-looklook

    5,158Ver en GitHub↗

    Este proyecto es una implementación de referencia y un plano arquitectónico para construir sistemas distribuidos utilizando el framework go-zero. Proporciona un boilerplate completo de microservicios y una estructura de proyecto estandarizada para arrancar servicios API y RPC con estructuras de carpetas consistentes. La implementación se distingue por proporcionar una guía completa y una base de código para el descubrimiento de servicios, limitación de tasa (rate limiting) y disyuntores (circuit breaking). Demuestra una integración de stack de observabilidad que coordina el rastreo distribuido, la recolección de métricas y el registro centralizado de logs a través de múltiples microservicios. El sistema cubre una amplia gama de capacidades distribuidas, incluyendo mensajería asíncrona mediante un modelo de publicación-suscripción, gestión de transacciones distribuidas para la consistencia de datos y un patrón de agregación de gateway para separar las solicitudes externas de la comunicación interna. También incluye generación automática de código a partir de definiciones y pipelines de entrega continua para el despliegue en contenedores.

    Features a zero-allocation router that minimizes memory overhead for high-performance request processing.

    Goasynqdtmelasticsearch
    Ver en GitHub↗5,158
  • openhft/chronicle-queueAvatar de OpenHFT

    OpenHFT/Chronicle-Queue

    3,692Ver en GitHub↗

    Chronicle Queue is a high-performance data handling system featuring off-heap message queues, memory-mapped file stores, and replicated message stores. It provides a binary compatible memory layout that enables different programming languages to share data without serialization overhead. The system utilizes a replicated message store to synchronize data across multiple nodes, ensuring high availability and instant failover. Its memory-mapped architecture supports deterministic replay from disk and low-latency data recording. The project implements off-heap memory management and zero-allocati

    Employs a zero-allocation architecture and off-heap memory to completely eliminate garbage collection pauses.

    Javachroniclejavalow-latency
    Ver en GitHub↗3,692
  • rust-embedded/embedded-halAvatar de rust-embedded

    rust-embedded/embedded-hal

    2,600Ver en GitHub↗

    Embedded-hal is a hardware abstraction layer for embedded microcontrollers that defines common traits allowing peripheral drivers to remain entirely independent of specific hardware platforms. The library provides platform-agnostic interfaces that decouple driver logic from microcontroller architectures, utilizing zero-cost trait abstractions that compile down to direct hardware register manipulations without runtime overhead or memory allocation. The project features asynchronous execution support and synchronous-to-asynchronous adaptation, enabling non-blocking peripheral operations and coo

    Provides stream and I/O traits that operate entirely without standard libraries or heap allocators.

    Rust
    Ver en GitHub↗2,600
  • rust-embedded/heaplessAvatar de rust-embedded

    rust-embedded/heapless

    1,977Ver en GitHub↗

    Heapless is an embedded Rust data structure library that provides statically allocated, fixed-capacity collections for memory-constrained systems. It implements a zero-allocation runtime model where all collection elements are stored inline within their own value structure, completely removing the need for operating system interaction, global allocators, or runtime heap allocation. Capacity is specified at compile time through generic type parameters, ensuring every collection has a fixed upper bound known before execution. The library implements core language traits to provide standard coll

    Operates without operating system interaction or global allocators, making data structures safe for bare-metal microcontrollers.

    Rustdata-structuresno-stdrust
    Ver en GitHub↗1,977
  • unicode-org/icu4xAvatar de unicode-org

    unicode-org/icu4x

    1,819Ver en GitHub↗

    ICU4X is a modular internationalization library written in Rust, designed as a cross-platform toolkit for formatting text, dates, numbers, and identifiers according to specific regional and cultural rules. It decomposes internationalization features into independent micro-libraries and embeds optimized binary structures directly into application binaries during the build phase via compile-time code generation, or loads externalized cultural datasets dynamically on demand. The library utilizes zero-allocation data structuring to access internationalization properties directly from serialized

    Accesses internationalization properties directly from serialized buffers without parsing or allocating dynamic heap memory at runtime.

    Rustcldricuinternationalization
    Ver en GitHub↗1,819
  • gobwas/globAvatar de gobwas

    gobwas/glob

    1,020Ver en GitHub↗

    Glob is a pattern matching library for Go that compiles wildcard strings and file paths into optimized matchers for high-throughput string validation and filtering. It evaluates text and file paths against character sets, ranges, and alternatives to determine if candidate inputs fit specific criteria. The library parses raw glob strings into structured syntax nodes before translating them into bytecode instruction sequences upfront. This compilation process enables finite state machine evaluations and zero-allocation path matching during runtime execution, preventing garbage collection press

    Executes string validations without allocating heap memory to prevent garbage collection pressure during high-frequency checks.

    Goglobgolangpattern
    Ver en GitHub↗1,020
  1. Home
  2. Software Engineering & Architecture
  3. Zero-Allocation Architectures

Explorar subetiquetas

  • Path MatchersZero-allocation matching techniques tailored for file paths and strings. **Distinct from Zero-Allocation Architectures:** Distinct from general zero-allocation architectures: specifically focuses on garbage-free path and string validation checks.
  • Routing ImplementationsSpecific implementations of zero-allocation routing for HTTP requests. **Distinct from Zero-Allocation Architectures:** Specializes zero-allocation architecture specifically for API routing rather than general data processing
  • Zero-Allocation Runtime ModelsRuntime architectures operating entirely without operating system interaction or global allocators. **Distinct from Zero-Allocation Architectures:** Distinct from Zero-Allocation Architectures: focuses specifically on runtime models for bare-metal microcontrollers devoid of OS or global allocators.