awesome-repositories.com
博客
MCP
awesome-repositories.com

通过 AI 驱动的搜索,发现最优秀的开源仓库。

探索精选搜索开源替代品自托管软件博客网站地图
项目MCP 服务器关于排名机制媒体报道
法律隐私政策服务条款
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

4 个仓库

Awesome GitHub RepositoriesExecution Context Isolation

Mechanisms to isolate service instances within specific execution flows to prevent data leakage.

Distinct from Dependency Scoping: Focuses on preventing data leakage between different concurrent execution flows (e.g. requests) rather than just module-level visibility.

Explore 4 awesome GitHub repositories matching devops & infrastructure · Execution Context Isolation. Refine with filters or upvote what's useful.

Awesome Execution Context Isolation GitHub Repositories

用 AI 发现最棒的仓库。我们将通过 AI 为您搜索最匹配的仓库。
  • effector/effectoreffector 的头像

    effector/effector

    4,837在 GitHub 上查看↗

    Effector is a reactive state management library designed for building complex, event-driven applications. It functions as a data flow engine that models application logic as a directed acyclic graph, ensuring that state updates propagate automatically through interconnected nodes. By utilizing atomic state updates and declarative unit composition, the library maintains data consistency and provides a predictable execution model for managing application state. The project distinguishes itself through its framework-agnostic architecture, which decouples business logic from user interface implem

    Scopes state and effects to specific execution contexts to support parallel testing and server-side rendering.

    TypeScriptbusiness-logiceffectorevent-driven
    在 GitHub 上查看↗4,837
  • typestack/typeditypestack 的头像

    typestack/typedi

    4,242在 GitHub 上查看↗

    TypeDI 是一个 TypeScript 依赖注入容器和控制反转工具。它作为一个集中式注册表和服务定位器,使用类型推断和装饰器来管理对象实例化并解耦组件依赖关系。 该项目提供作用域依赖管理,以在特定上下文中隔离服务实例,防止不同执行流之间的数据泄漏。它通过使用类型安全令牌以及将唯一标识符或类构造函数映射到特定服务实例的能力,支持灵活的服务解析。 该容器涵盖了全面的服务生命周期管理,包括单例和瞬态生命周期,以及循环引用的解析。它包括服务分组、基于工厂的实例化以及与外部框架集成的功能。为了质量保证,该系统提供了用于依赖模拟和重置容器状态的实用程序,以确保单元测试期间的隔离。

    Provides scoped dependency management to isolate service instances within specific contexts and prevent data leakage between execution flows.

    TypeScriptdependency-injectioninversion-of-controlioc
    在 GitHub 上查看↗4,242
  • dromara/liteflowdromara 的头像

    dromara/liteflow

    3,779在 GitHub 上查看↗

    Liteflow is a component-based rule engine and workflow orchestrator used to define business logic through a chain of reusable components. It utilizes a structured data language to map logic paths, functioning as a dynamic workflow engine for managing sequences of synchronous and asynchronous tasks. The project is distinguished by its support for hot deployment, allowing rule definitions and execution logic to be updated in real time without restarting the application. It also features a multi-language scripting engine that embeds external scripts into business rules to enable flexible logic c

    Maintains separate data environments for each workflow instance to prevent state leakage during concurrent execution.

    Javaai-agentai-agentscomponent
    在 GitHub 上查看↗3,779
  • vercel/workflowvercel 的头像

    vercel/workflow

    1,718在 GitHub 上查看↗

    Workflow is a platform for executing long-running, stateful processes that automatically persist progress and recover state after system interruptions. It functions as a durable orchestration engine designed to manage complex, multi-step asynchronous operations within distributed systems. The framework distinguishes itself through event-sourcing and checkpointing mechanisms that record execution steps as an immutable log, allowing for precise state reconstruction after failures. It provides sandboxed task isolation to run side-effect-heavy logic in restricted environments, ensuring that sensi

    Isolates sensitive logic within specific execution flows to prevent unintended interference between components.

    TypeScript
    在 GitHub 上查看↗1,718
  1. Home
  2. DevOps & Infrastructure
  3. Dependency Management
  4. Environment and Scoping Controls
  5. Dependency Scoping
  6. Execution Context Isolation