service-registry

name	service-registry
description	Registers external services with health checks, central config, and unified execution. Use when integrating multiple external services needing coordination.
alwaysApply	false
category	infrastructure
tags	["services","registry","execution","health-checks","integration"]
dependencies	["quota-management","usage-logging"]
tools	[]
provides	{"infrastructure":["service-registry","health-monitoring","execution-engine"],"patterns":["service-discovery","unified-execution","configuration-management"]}
usage_patterns	["multi-service-integration","service-health-checks","unified-execution","configuration-management"]
complexity	intermediate
model_hint	standard
estimated_tokens	550
progressive_loading	true
modules	["modules/service-config.md","modules/execution-patterns.md"]

Table of Contents

• Overview
• When to Use
• Core Concepts
• Service Configuration
• Execution Result
• Quick Start
• Register Services
• Execute via Service
• Health Checks
• Service Selection
• Auto-Selection
• Failover Pattern
• Integration Pattern
• Detailed Resources
• Exit Criteria

Service Registry

Overview

A registry pattern for managing connections to external services. Handles configuration, health checking, and execution across multiple service integrations.

When To Use

• Managing multiple external services.
• Need consistent execution interface.
• Want health monitoring across services.
• Building service failover logic.

When NOT To Use

• Single service integration without registry needs

Core Concepts

Service Configuration

@dataclass
class ServiceConfig:
    name: str
    command: str
    auth_method: str  # "api_key", "oauth", "token"
    auth_env_var: str
    quota_limits: dict
    models: list[str] = field(default_factory=list)

Verification: Run the command with --help flag to verify availability.

Execution Result

@dataclass
class ExecutionResult:
    success: 
    stdout: 
    stderr: 
    exit_code: 
    duration: 
    tokens_used: