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
·

57 repositorios

Awesome GitHub RepositoriesMessage Queues

Systems for sequencing and managing the flow of outgoing messages to prevent target or sender overload.

Distinct from Queue Management: Focuses on the sequencing of communication payloads rather than background worker task prioritization

Explore 57 awesome GitHub repositories matching devops & infrastructure · Message Queues. Refine with filters or upvote what's useful.

Awesome Message Queues GitHub Repositories

Encuentra los mejores repositorios con IA.Buscaremos los repositorios que mejor coincidan usando IA.
  • whalefell/smsboomAvatar de WhaleFell

    WhaleFell/SMSBoom

    15,192Ver en GitHub↗

    SMSBoom is an automated SMS bomber and bulk messaging tool designed to send a rapid succession of text messages to a target phone number or a list of multiple recipients. It functions as a bulk SMS sender that automates the dispatch of large volumes of text messages. The project manages mass communication workflows through automated text dispatch and bulk messaging capabilities. It utilizes a system for sending messages to multiple recipients simultaneously via automated messaging systems. The tool handles message dispatching via HTTP requests to third party gateways, employing concurrent re

    Organizes target phone numbers into a sequential queue to manage the flow of bulk messages.

    Python
    Ver en GitHub↗15,192
  • rabbitmq/rabbitmq-serverAvatar de rabbitmq

    rabbitmq/rabbitmq-server

    13,732Ver en GitHub↗

    RabbitMQ is a multi-protocol messaging broker that functions as an AMQP message broker, a clustered message queue, and a distributed message stream. It provides a server for translating and bridging communication between diverse messaging standards to connect heterogeneous systems. The system distinguishes itself through distributed broker clustering and federation, using shoveling mechanisms to synchronize data across geographically separate sites. It supports high-throughput, append-only logs for persisting and reading large sequences of messages for real-time processing. The broker covers

    Manages the routing logic and relationships between specialized exchanges and queues, including delayed delivery.

    JavaScript
    Ver en GitHub↗13,732
  • provectus/kafka-uiAvatar de provectus

    provectus/kafka-ui

    12,158Ver en GitHub↗

    kafka-ui is a web interface and centralized control plane for administering Apache Kafka clusters, topics, and brokers. It functions as a distributed message queue dashboard and orchestrator, allowing for the oversight of multiple distributed Kafka environments from a single management interface. The project provides dedicated tools for producing and inspecting messages within topics using various serialization and encoding formats. It includes a schema registry client for defining and versioning data schemas and a consumer monitoring dashboard to track offsets and calculate partition lag. T

    Functions as a centralized monitoring system for tracking cluster health and consumer lag across environments.

    Javaapache-kafkabig-datacluster-management
    Ver en GitHub↗12,158
  • eosio/eosAvatar de EOSIO

    EOSIO/eos

    11,189Ver en GitHub↗

    EOS is a Layer 1 blockchain infrastructure and high-throughput transaction engine. It serves as a WebAssembly smart contract platform that manages state transitions and network consensus across a peer-to-peer network. The system utilizes a sandboxed virtual machine for executing smart contract logic and employs a Byzantine Fault Tolerant delegated proof-of-stake consensus mechanism to finalize the global ledger state. It features a resource-based stake model for CPU and memory allocation and an asynchronous messaging system for inter-contract communication to prevent recursive call overflows.

    Triggers inter-contract actions using an asynchronous queue to prevent recursive call overflows.

    C++eosio
    Ver en GitHub↗11,189
  • zeromq/libzmqAvatar de zeromq

    zeromq/libzmq

    10,902Ver en GitHub↗

    libzmq is a C++ based asynchronous messaging engine and networking core designed for routing non-blocking messages between distributed nodes. It functions as a distributed message queue that implements the ZMTP wire-format framing protocol to standardize how data moves across different network transport layers. The library provides a multi-transport abstraction that allows a single interface to route data across TCP, IPC, and in-process memory. It incorporates a cryptographic layer to encrypt and authenticate transmissions between nodes and employs topology-based messaging patterns, such as p

    Implements internal buffers to decouple senders and receivers for non-blocking communication.

    C++concurrencylibzmqmessaging
    Ver en GitHub↗10,902
  • dtm-labs/dtmAvatar de dtm-labs

    dtm-labs/dtm

    10,881Ver en GitHub↗

    dtm is a distributed transaction framework and polyglot transaction coordinator designed to maintain data consistency across microservices. It functions as a Saga orchestration engine and a two-phase message coordinator, ensuring that multi-service operations either succeed completely or roll back to a consistent state. The project distinguishes itself by supporting multiple consistency patterns, including Saga, TCC, XA, and outbox patterns, allowing users to select the appropriate model for their specific application requirements. It provides a polyglot integration layer via HTTP and gRPC, e

    Triggers remote service calls asynchronously without requiring dedicated message queue infrastructure.

    Gocadencecsharpdatabase
    Ver en GitHub↗10,881
  • sfyc23/everydaywechatAvatar de sfyc23

    sfyc23/EverydayWechat

    10,296Ver en GitHub↗

    EverydayWechat is a WeChat automation bot designed to automate messages, scheduled reminders, and automatic replies within the WeChat messaging ecosystem. It functions as a multi-purpose system that combines the roles of a scheduled message sender, an auto-reply bot, and a chatbot assistant. The project enables the delivery of customized recurring messages to specific users and group chats on a fixed timetable. It also provides automated individual replies based on preconfigured rules and group chat assistance that fetches real-time data for weather, logistics, and calendars. The system inco

    Implements a message queue to sequence outgoing messages and avoid platform rate limits.

    Pythonaiautoreplybot
    Ver en GitHub↗10,296
  • tporadowski/redisAvatar de tporadowski

    tporadowski/redis

    9,987Ver en GitHub↗

    Redis is a high-performance in-memory key-value store that functions as a distributed cache, message broker, and NoSQL database. It provides sub-millisecond read and write access to data stored in RAM and can operate as a vector database for indexing high-dimensional embeddings. The system supports a wide range of data storage and synchronization primitives, including the management of strings, hashes, lists, sets, and JSON documents. It enables real-time data operations through atomic transactions, hybrid persistence using snapshots and append-only logs, and high-availability configurations

    Implements asynchronous message queues using lists and sorted sets for task sequencing.

    Credisredis-for-windowsredis-msi-installer
    Ver en GitHub↗9,987
  • happydog-intj/jsbridgeAvatar de happydog-intj

    happydog-intj/JsBridge

    9,912Ver en GitHub↗

    JsBridge is a bidirectional communication layer for Android that synchronizes data and triggers actions between a native Java application and an embedded web view. It serves as an interface for calling Java methods from JavaScript and executing JavaScript functions from native Android code. The project features an asynchronous bridge queue that stores pending function calls in a readiness buffer, ensuring requests are executed only after the connection between the native and web environments is stable. It utilizes callback identifier mapping to route asynchronous native responses back to the

    Implements a message-queueing buffer that stores calls until the native and web environments are stable.

    Java
    Ver en GitHub↗9,912
  • resque/resqueAvatar de resque

    resque/resque

    9,480Ver en GitHub↗

    Resque is a Ruby library for enqueueing and processing asynchronous tasks using Redis as a data store. It functions as a distributed task processor and queue manager, allowing long-running work to be moved out of the main request cycle. The system executes background jobs in isolated child processes to prevent memory leaks and provides a web-based dashboard for monitoring queue depths, worker activity, and failed job statistics. Capability areas include distributed worker coordination via signals, error handling with job retry mechanisms, and priority-ordered queue management. It also suppor

    Provides a visual dashboard for tracking queue depths and the overall health of the task system.

    Rubyasynchronous-tasksasynctaskbackground-jobs
    Ver en GitHub↗9,480
  • apachecn/interviewAvatar de apachecn

    apachecn/Interview

    8,944Ver en GitHub↗

    This project is a comprehensive knowledge base and study resource designed for mastering technical interviews. It provides structured guides, roadmaps, and curricula focused on data structures, algorithms, system design, and frontend engineering to help candidates prepare for software engineering screenings. The repository distinguishes itself by offering a holistic approach to professional advancement. Beyond technical drills, it includes a career development handbook covering resume optimization, salary benchmarking, and strategic negotiation coaching. It also provides detailed methodologie

    Uses message queues to decouple producers and consumers for scalable asynchronous request processing.

    Jupyter Notebookinterviewkaggleleetcode
    Ver en GitHub↗8,944
  • appleboy/gorushAvatar de appleboy

    appleboy/gorush

    8,738Ver en GitHub↗

    Gorush is a dedicated notification dispatch server used to send real-time alerts to iOS and Android mobile devices. It functions as a centralized infrastructure for hosting a notification API and managing the delivery of push messages through high-throughput queuing. The system supports both gRPC streams and HTTP endpoints to receive notification triggers and includes a command-line interface for triggering alerts without a running server process. It manages network traffic through proxy routing via HTTP or SOCKS5 and secures server communication using automated TLS certificate management. O

    Uses a configurable pool of concurrent workers and queues to handle high-volume notification throughput.

    Goandroidapnsgcm
    Ver en GitHub↗8,738
  • taskforcesh/bullmqAvatar de taskforcesh

    taskforcesh/bullmq

    8,432Ver en GitHub↗

    BullMQ is a Redis-backed message queue library and background processor designed for distributed task queueing. It functions as a distributed queue manager and task scheduler, utilizing Redis to manage asynchronous job processing and persistence. The system distinguishes itself through its role as a job workflow orchestrator, enabling the definition of complex parent-child job dependencies and hierarchies for multi-step workflows. It provides sandboxed process execution to isolate heavy workloads and prevent event loop blocking, alongside distributed rate limiting to protect downstream servic

    Provides persistent message queues to decouple services and ensure delivery when receivers are offline.

    TypeScriptbackground-jobselixirnodejs
    Ver en GitHub↗8,432
  • swiftkickmobile/swiftmessagesAvatar de SwiftKickMobile

    SwiftKickMobile/SwiftMessages

    7,556Ver en GitHub↗

    SwiftMessages is an iOS notification bar library and in-app message queue manager. It provides a system for displaying customizable alerts and status messages at the top, bottom, or center of the screen. The library features a hosting bridge that allows declarative SwiftUI views to be rendered within imperative UIKit containers. It includes a queue management system that sequences chronological notifications and filters duplicate alerts to prevent interface overlap. The system handles dynamic layout management to avoid occlusion by the system keyboard and provides an accessibility interface

    Implements a sequencing system to manage notification flow and prevent UI overlap.

    Swift
    Ver en GitHub↗7,556
  • terry-mao/goimAvatar de Terry-Mao

    Terry-Mao/goim

    7,376Ver en GitHub↗

    goim

    Provides a Kafka-driven message queue server for asynchronous, non-blocking fan-out delivery to subscribers.

    Go
    Ver en GitHub↗7,376
  • dyc87112/springcloud-learningAvatar de dyc87112

    dyc87112/SpringCloud-Learning

    7,375Ver en GitHub↗

    SpringCloud-Learning is an educational project that demonstrates how to build microservices using Spring Cloud, covering the core patterns of service discovery, centralized configuration management, and API gateway routing. The project provides hands-on examples for registering and discovering microservice instances with Nacos, Eureka, or Consul, and for routing external API requests through Spring Cloud Gateway with support for filters and load balancing. The tutorials explore service resilience through circuit breakers and rate limiting with Sentinel and Hystrix, including custom fallback l

    Re-injects failed messages back into the queue for retry until processing succeeds.

    Javaconsuleurekahystrix
    Ver en GitHub↗7,375
  • needim/notyAvatar de needim

    needim/noty

    6,625Ver en GitHub↗

    Noty is a dependency-free JavaScript toast notification library and in-app notification system. It provides a framework for rendering non-blocking alert, success, error, and information messages, as well as interactive confirmation dialogs. The library includes a notification queue manager to organize the sequence and timing of messages and a web push notification manager for delivering system-level alerts via service workers when an application is inactive. The system supports extensive visual customization through HTML templates and theme configurations. It manages the notification lifecyc

    Organizes incoming notifications into ordered lists to control their appearance timing and sequence.

    JavaScript
    Ver en GitHub↗6,625
  • hatchet-dev/hatchetAvatar de hatchet-dev

    hatchet-dev/hatchet

    6,622Ver en GitHub↗

    Hatchet is an open-source durable workflow engine and task orchestration platform. It provides a framework for building and executing fault-tolerant, multi-step pipelines as directed acyclic graphs (DAGs), with automatic retries, scheduling, and real-time observability. The system is built around durable task checkpointing, which persists execution state after each step so work can resume from the last checkpoint after a worker crash or restart, and it supports event-driven task resumption that pauses a task until a matching external event arrives. The platform distinguishes itself through it

    Selects RabbitMQ as the task queue backend and tunes requeue limits, queue sizes, and QoS settings.

    Goconcurrencydagdistributed
    Ver en GitHub↗6,622
  • webhooksite/webhook.siteAvatar de webhooksite

    webhooksite/webhook.site

    6,620Ver en GitHub↗

    Webhook.site is a web-based tool that captures, inspects, and debugs incoming HTTP requests and emails sent to a unique URL, without requiring any server setup. It also functions as an API mocking and response modification tool, capable of generating mock APIs from OpenAPI specifications and altering HTTP responses, headers, and status codes for testing purposes. Beyond inspection, it serves as a platform for webhook automation and workflow orchestration, triggering multi-step automations—including database queries, SSH commands, and HTTP calls—when a webhook is received. The service distingu

    Publishes messages to RabbitMQ queues with configurable server connections.

    JavaScriptangularfrontendlaravel
    Ver en GitHub↗6,620
  • threedotslabs/wild-workouts-go-ddd-exampleAvatar de ThreeDotsLabs

    ThreeDotsLabs/wild-workouts-go-ddd-example

    6,348Ver en GitHub↗

    This project is a reference implementation of Domain-Driven Design, Clean Architecture, and Command Query Responsibility Segregation (CQRS) patterns using the Go programming language. It serves as a sample application to demonstrate how to decouple core domain rules from infrastructure and delivery mechanisms. The system is built as a gRPC microservices architecture, utilizing type-safe communication and service contracts. It implements an event-driven architecture to manage eventual consistency and asynchronous processing, specifically employing the Outbox pattern to ensure reliable messagin

    Publishes asynchronous events to message brokers to enable reactive system changes without blocking requests.

    Goclean-architecturecqrsddd
    Ver en GitHub↗6,348
Ant.123Siguiente
  1. Home
  2. DevOps & Infrastructure
  3. Queue Management
  4. Message Queues

Explorar subetiquetas

  • Asynchronous Message Publishing1 sub-etiquetaMechanisms for sending data from web endpoints to message brokers for background processing. **Distinct from Message Queues:** Focuses on the act of publishing from an HTTP handler, whereas the parent focuses on the general flow and sequencing of messages.
  • Bridge Readiness QueuesQueues that buffer messages until a specific connection state is reached between two environments. **Distinct from Message Queues:** Distinct from Asynchronous Task Queues by targeting the synchronization of native and web runtime readiness.
  • Broker Test Message PublishersCLI tools for manually sending messages to a broker for debugging consumers. **Distinct from RabbitMQ Publishers:** Focuses on manual debugging tools rather than production RabbitMQ publishing logic.
  • Cloudflare Queue ManagementManaging Cloudflare Queues including creation, deletion, message sending, and consumer updates. **Distinct from Message Queues:** Distinct from Message Queues: specifically targets Cloudflare's queue service, not general message queue implementations.
  • Deferred Notification Queues1 sub-etiquetaQueues that defer action notifications to prevent recursive call overflows during execution. **Distinct from Message Queues:** Specifically addresses the prevention of recursive stack overflows in smart contracts via deferred execution, not general message sequencing.
  • Dynamic ProvisioningAutomatically creating message queues on demand based on request patterns. **Distinct from Message Queues:** Focuses on the automatic creation of queues rather than general configuration or sequencing.
  • Kafka-Driven Message Queue ServersMessage delivery servers that queue outgoing messages through Kafka for asynchronous, non-blocking fan-out to subscribers. **Distinct from Message Queues:** Distinct from Message Queues: focuses on a Kafka-backed server that queues and delivers messages, not the queue implementation itself.
  • Message Consumption4 sub-etiquetasThe process of retrieving messages from a queue, including long-polling and visibility management. **Distinct from Message Queues:** Focuses on the operational act of consuming messages from the queue rather than queue configuration.
  • Message Queue Configurations8 sub-etiquetasSelects and tunes message queue backends like RabbitMQ with requeue limits, queue sizes, and QoS settings. **Distinct from Message Queues:** Distinct from Message Queues: focuses on the configuration and tuning of message queue backends, not the queue implementation itself.
  • Message Queue DashboardsVisual monitoring interfaces for tracking the health and throughput of message queues. **Distinct from Message Queues:** Focuses on the dashboarding/observability layer rather than the queue implementation itself.
  • Message Queue Resilience TestingValidation methods for ensuring message consumers handle malformed inputs without crashing. **Distinct from Message Queues:** Focuses on testing the resilience of the consumer logic rather than the management of the queue infrastructure.
  • Notification Delivery QueuesQueuing mechanisms designed for the asynchronous dispatch and retry of push notifications. **Distinct from Message Queues:** Focuses on delivery reliability and retries for notifications rather than general message sequencing
  • Off-Heap QueuesMessage queues that store data in native memory to avoid garbage collection pauses. **Distinct from Message Queues:** Specifically targets the off-heap memory implementation rather than general queue management or configuration.
  • Queue Content InspectionUtilities for retrieving and validating the content of messages within a queue. **Distinct from Message Queues:** Focuses on inspecting and asserting the contents of a queue rather than managing the flow of messages.
  • Queue EmulationImplementation of message queue interfaces to mimic specific external service providers. **Distinct from Message Queues:** Focuses on the emulation aspect rather than general queue sequencing.
  • Queue State VerificationUtilities for asserting the state of a queue, such as whether it is empty or contains a specific count of messages. **Distinct from Message Queues:** Focuses on state assertions for testing rather than the general sequencing and management of payloads.
  • RabbitMQ Publishers2 sub-etiquetasSends messages to RabbitMQ queues using specified server connection details. **Distinct from Message Queues:** Distinct from Message Queues: focuses on publishing to RabbitMQ specifically, not general message queue management.
  • Socket Event Synchronization Queues2 sub-etiquetasShared message queues that synchronize real-time events and session state across multiple server worker processes for horizontal scaling. **Distinct from Message Queues:** Distinct from Message Queues: focuses on coordinating real-time socket events across distributed workers, not general task sequencing.
  • Table-Based StorageUse of relational database tables as the primary persistence layer for message queues. **Distinct from Message Queues:** Focuses on the use of standard database tables rather than cloud object storage or log-structured files.
  • UI Message SequencingLogic for ordering the appearance and timing of user-facing alerts in a sequence. **Distinct from Message Queues:** Focuses on the temporal display of UI alerts rather than backend infrastructure for message delivery.