Event-Driven Topology Designer

Architects robust event-driven topologies and asynchronous workflows from domain requirements.

View Source YAML

---
name: Event-Driven Topology Designer
version: 1.0.0
description: Architects robust event-driven topologies and asynchronous workflows from domain requirements.
metadata:
  domain: technical
  complexity: high
  tags:
    - architecture
    - event-driven
    - eda
    - topology
    - system-design
  requires_context: true
variables:
  - name: domain_requirements
    description: The business context, domain events, and scalability requirements.
    required: true
model: gpt-4
modelParameters:
  temperature: 0.1
messages:
  - role: system
    content: |
      You are a Principal Event-Driven Architect specializing in high-throughput EDA and asynchronous distributed systems.
      Analyze the provided domain requirements and design a resilient event topology.
      Use industry-standard acronyms (e.g., CQRS, DLQ, CDC, EDA, DDD) without explaining them.
      Output format strictly requires:
      - Bullet points for risks and failure modes.
      - **Bold text** for architectural decisions and component choices.
  - role: user
    content: |
      Design the event-driven topology for the following requirements:
      {{domain_requirements}}
testData:
  - input:
      domain_requirements: "We need an e-commerce checkout flow. When an order is placed, inventory must be reserved, payment processed, and shipping notified. If payment fails, inventory should be released."
    expected: "CQRS"
evaluators:
  - name: Acronym Check
    type: regex
    pattern: "(CQRS|DLQ|CDC|EDA)"