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

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

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

4 个仓库

Awesome GitHub RepositoriesTask-Based Execution Models

Systems that map named functions to configuration objects to drive a workflow.

Distinct from Task Execution Sequencing: Distinct from Task Execution Sequencing by focusing on the structural model of mapping functions to config rather than just the order of execution.

Explore 4 awesome GitHub repositories matching development tools & productivity · Task-Based Execution Models. Refine with filters or upvote what's useful.

Awesome Task-Based Execution Models GitHub Repositories

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

    gruntjs/grunt

    12,243在 GitHub 上查看↗

    Grunt is a build automation tool and JavaScript task runner. It serves as a Node.js automation framework designed to execute automated workflows for building, testing, and deploying software projects. The system functions as a task runner that automates repetitive development chores such as minification, compilation, and testing. It provides orchestration for development tasks, frontend asset pipelines, and continuous integration workflows. The framework utilizes a task-based execution model where developers define a sequence of named functions. This is supported by a plugin-based extensibil

    Runs a sequence of named functions mapped to configuration objects to automate development workflows.

    JavaScript
    在 GitHub 上查看↗12,243
  • changmingxie/tcc-transactionchangmingxie 的头像

    changmingxie/tcc-transaction

    5,768在 GitHub 上查看↗

    本项目是一个 Java 实现的 Try-Confirm-Cancel (TCC) 模式,提供了一个分布式事务框架和管理库。它作为一个协调器,管理多阶段事务的生命周期,以确保跨多个分布式服务的一致性。 该框架包括一个分布式事务协调器服务器,用于从本地服务卸载事件和任务操作。它还提供了一个专用仪表板,用于可视化事务状态并手动操作分布式事件和任务。 该系统通过三阶段提交协议和异步重试机制来管理一致性,以实现最终一致性。它支持用于持久化事务状态的可插拔后端存储,并利用基于任务的工作流来执行分布式操作。

    Decomposes complex distributed transactions into individual tasks processed according to the TCC lifecycle.

    Java
    在 GitHub 上查看↗5,768
  • dotnet/msbuilddotnet 的头像

    dotnet/msbuild

    5,519在 GitHub 上查看↗

    MSBuild is a .NET build engine and software build automation system that transforms source code into deployable applications. It utilizes a declarative project system based on a structured XML schema to define build items, properties, and targets used across the .NET ecosystem and Visual Studio. The system features a customizable build task framework that allows the implementation of custom tasks and loggers to perform specific software construction operations. This extensibility enables the creation of specialized logic to modify build process behavior. The engine manages build automation t

    Encapsulates build work into reusable task classes that perform specific file or system transformations.

    C#buildhacktoberfesthelp-wanted
    在 GitHub 上查看↗5,519
  • microsoft/msbuildMicrosoft 的头像

    Microsoft/msbuild

    5,519在 GitHub 上查看↗

    MSBuild is a task-based build engine and programmatic framework used to compile and package .NET applications. It functions as a customizable orchestrator that executes sequences of targets to automate software compilation and deployment workflows using a structured XML-based configuration schema. The system allows for the creation of custom build tasks and reusable rules to handle unique compilation requirements. It supports multi-target framework development, enabling a single codebase to be compiled against various runtime versions to ensure compatibility across different platforms. The e

    Encapsulates build work as executable classes that process input items to produce output files.

    C#
    在 GitHub 上查看↗5,519
  1. Home
  2. Development Tools & Productivity
  3. Parallel Execution
  4. Task Execution Sequencing
  5. Task-Based Execution Models

探索子标签

  • TCC Workflow ExecutionsExecution models that decompose distributed transactions into Try-Confirm-Cancel task sequences. **Distinct from Task-Based Execution Models:** Specific to the TCC lifecycle phases rather than general function-to-config mapping.