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
·

10 repositorios

Awesome GitHub RepositoriesWorker Process Isolation

Executing asynchronous jobs in separate operating system processes to protect the main server's responsiveness.

Distinct from Polling-Based Worker Execution: Focuses on the architectural isolation of the worker process from the API server, rather than the polling mechanism.

Explore 10 awesome GitHub repositories matching devops & infrastructure · Worker Process Isolation. Refine with filters or upvote what's useful.

Awesome Worker Process Isolation GitHub Repositories

Encuentra los mejores repositorios con IA.Buscaremos los repositorios que mejor coincidan usando IA.
  • vendurehq/vendureAvatar de vendurehq

    vendurehq/vendure

    7,924Ver en GitHub↗

    Vendure is a Node.js e-commerce engine and headless commerce framework built with NestJS and TypeScript. It serves as a multi-channel commerce platform that manages product catalogs, orders, and customers via a strongly typed GraphQL API. The platform is distinguished by its highly extensible architecture, featuring a customizable administrative dashboard where developers can inject custom React components and entity views. It supports multi-channel commerce, allowing the isolation of products, currencies, and regional catalogs from a single unified backend. The engine covers a broad range o

    Runs asynchronous jobs in a dedicated worker process to keep the main server responsive.

    TypeScriptecommerceecommerce-apiecommerce-framework
    Ver en GitHub↗7,924
  • versatica/mediasoupAvatar de versatica

    versatica/mediasoup

    7,146Ver en GitHub↗

    Mediasoup is a selective forwarding unit used for real-time media routing. It enables the development of low-latency audio and video communication systems by routing streams between participants without transcoding. The project provides embedded media routing logic that can be integrated directly into an application. It supports simulcast and quality layering, allowing the system to adapt resolution and bitrate based on real-time bandwidth estimations to maintain connection stability. The capability surface includes media track management for audio, video, and screen capture, as well as bidi

    Implements native C++ worker processes to isolate heavy media processing from the main JavaScript event loop.

    C++c-plus-plusnodejsrust
    Ver en GitHub↗7,146
  • apache/stormAvatar de apache

    apache/storm

    6,683Ver en GitHub↗

    Storm is a distributed stream processing framework designed to execute unbounded computations across a cluster to process real-time data streams. It functions as a data pipeline orchestrator that allows users to define and deploy declarative data flow graphs connecting streaming sources to processing components. The system operates as a multi-tenant distributed compute engine that isolates workloads and limits resource usage across shared clusters using dedicated pools and access control. It is also a secure distributed processing engine that employs encrypted node communication and SSL-secur

    Launches worker processes using the operating system identity of the submitting user to ensure correct permissioning.

    Java
    Ver en GitHub↗6,683
  • apache/pinotAvatar de apache

    apache/pinot

    6,098Ver en GitHub↗

    Pinot is a distributed, columnar analytical database designed for high-concurrency, low-latency query processing. It functions as a real-time OLAP datastore, enabling interactive, user-facing analytics by ingesting and querying massive datasets from both streaming and batch sources. The system architecture relies on a centralized controller for cluster coordination and a distributed segment-based storage model to ensure horizontal scalability. The platform distinguishes itself through a hybrid ingestion pipeline that unifies real-time event streams and historical batch data into a single quer

    Assigns specific data processing workloads to designated worker nodes to manage resource allocation and prevent interference.

    Java
    Ver en GitHub↗6,098
  • pydantic/montyAvatar de pydantic

    pydantic/monty

    5,540Ver en GitHub↗

    Monty is a sandboxed execution environment designed primarily for running Python code generated by AI models. It provides a secure, isolated runtime that blocks host access, enforces resource limits, and supports pre-execution type checking against built-in type hints to catch signature mismatches before code runs. The sandbox can persist its interpreter state at external function calls, allowing execution sessions to be serialized, stored, and later resumed from a file or database. What distinguishes Monty is its combination of stateful, resumable execution with multi-language native embeddi

    Executes each request in a separate operating system process, automatically replacing crashed workers to ensure reliability.

    Rust
    Ver en GitHub↗5,540
  • buildbot/buildbotAvatar de buildbot

    buildbot/buildbot

    5,452Ver en GitHub↗

    Buildbot es un framework de integración continua (CI) basado en Python y un orquestador de builds distribuido. Funciona como un motor de automatización de builds que coordina la obtención del código fuente, la ejecución de pasos de compilación y la generación de informes a través de un controlador central y una red de agentes trabajadores remotos. El sistema se distingue por su arquitectura de extensibilidad basada en plugins y un modelo de distribución maestro-trabajador. Permite la modificación dinámica de los builds en tiempo de ejecución y admite un backend de base de datos conectable para persistir el estado del sistema y el historial de builds. El proyecto cubre una amplia gama de capacidades, incluyendo la programación automatizada de builds y la orquestación de pipelines, integración con control de versiones mediante polling y webhooks, y el aprovisionamiento de trabajadores en servidores físicos, contenedores Docker y clusters de Kubernetes. También proporciona monitorización y observabilidad integral mediante el análisis de logs de build y seguimiento de rendimiento, junto con gestión segura de secretos y autenticación multi-proveedor. El control administrativo está disponible a través de una interfaz web dedicada y herramientas de línea de comandos para la validación de configuración y gestión de procesos.

    Automatically isolates and suspends workers encountering preparation issues using an exponential back-off timer.

    Python
    Ver en GitHub↗5,452
  • emmett-framework/granianAvatar de emmett-framework

    emmett-framework/granian

    5,074Ver en GitHub↗

    Granian is a Rust-based HTTP server written specifically to serve Python web applications. It supports the three major Python gateway interfaces—ASGI for asynchronous apps, WSGI for synchronous apps, and RSGI for async requests—while also handling HTTP/1.1, HTTP/2, and WebSocket connections through automatic protocol negotiation. Architecturally, Granian uses a multiprocess worker model that isolates requests across CPU cores and provides configurable threadpool-limited concurrency to control backpressure per worker. It includes built-in Prometheus metrics exposition for connection counts and

    Uses multiple worker processes to isolate requests across CPU cores.

    Rustasgiasynciohttp
    Ver en GitHub↗5,074
  • azkaban/azkabanAvatar de azkaban

    azkaban/azkaban

    4,504Ver en GitHub↗

    Azkaban es un gestor de flujos de trabajo distribuido y orquestador de trabajos basado en DAG, diseñado como un procesador de lotes empresarial. Sirve como un motor de flujo de trabajo basado en Java que programa y ejecuta secuencias complejas de trabajos a través de un cluster de servidores ejecutores, con funcionalidad específica para gestionar cargas de trabajo de big data en clusters Hadoop. El sistema se distingue por un modelo de ejecutor distribuido que coordina el estado a través de una base de datos compartida para asegurar la alta disponibilidad. Emplea una arquitectura basada en plugins que permite tipos de trabajo personalizados y extensiones de funcionalidad del sistema, incluyendo la capacidad de recargar plugins en caliente sin reiniciar los servidores ejecutores. La plataforma cubre una amplia gama de capacidades, incluyendo la orquestación de pipelines de datos con lógica condicional, programación periódica y basada en eventos, y monitoreo empresarial con seguimiento de SLA. Proporciona control de acceso granular y suplantación de identidad de usuario para una ejecución segura, junto con herramientas de gestión de tráfico para el balanceo de carga de ejecutores y cuotas de recursos. Los usuarios pueden gestionar los flujos de trabajo a través de una interfaz basada en web o programáticamente mediante una API de ejecución de flujos de trabajo.

    Executes processes under the security identity of the submitting user to enforce cluster permissions.

    Java
    Ver en GitHub↗4,504
  • jorisvink/koreAvatar de jorisvink

    jorisvink/kore

    3,825Ver en GitHub↗

    Kore is an event-driven web and WebSocket server framework designed for building high-performance web services and APIs in C or Python. It functions as a secure, concurrent application framework that utilizes non-blocking I/O and isolated worker processes to handle high-concurrency traffic. The project is distinguished by a security-first architecture that features OS-level process sandboxing, privilege separation, and the isolation of private encryption keys into dedicated processes. It enables zero-downtime deployments through dynamic module hot-reloading and provides automated TLS certific

    Employs an isolated worker process model that spawns separate processes per CPU core for high-concurrency handling.

    Ccframeworkhigh-performance
    Ver en GitHub↗3,825
  • sozu-proxy/sozuAvatar de sozu-proxy

    sozu-proxy/sozu

    3,687Ver en GitHub↗

    Sozu is a high-performance, memory-safe reverse proxy and load balancer built in Rust. It is designed to manage HTTP, TCP, and UDP traffic through a multi-process architecture that leverages isolated worker processes to ensure fault tolerance and efficient resource utilization across multi-core hardware. The project distinguishes itself through a focus on continuous availability and dynamic control. It features a unique binary hot-reloading mechanism and a Unix-socket-based control plane, allowing administrators to update proxy configurations, modify listener settings, and even replace the pr

    Restricts worker process privileges to shield backend infrastructure and prevent unauthorized access to system resources.

    Rusthttphttp-proxyperformance
    Ver en GitHub↗3,687
  1. Home
  2. DevOps & Infrastructure
  3. Polling-Based Worker Execution
  4. Worker Process Isolation

Explorar subetiquetas

  • Unstable Worker IsolationTemporarily suspends workers that experience preparation failures using back-off timers. **Distinct from Worker Process Isolation:** Distinct from general process isolation: focuses on the temporal suspension of failing workers via back-off logic.
  • User Identity ExecutionLaunching worker processes using the specific operating system identity of the user who submitted the task. **Distinct from Worker Process Isolation:** Focuses on OS-level user identity for process execution rather than general process isolation from a server.