skills.rest
basabecode
basabecodeCOMMUNITY
Explore all skills by this author →
GitHub

eda-architect

Design event-driven architectures with sagas and event contracts for cross-portal workflows.

Updated Aug 23, 2026
Search Tags:#architecture#patterns#orchestration#event-driven#eda#cross-portal
One-click install
npx skills add https://github.com/basabecode/SomosTecnicos --skill eda-architect-basabecode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eda-architect
Source: https://github.com/basabecode/SomosTecnicos/tree/main/.agents/skills/eda-architect
Command: npx skills add https://github.com/basabecode/SomosTecnicos --skill eda-architect-basabecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EDA Architect helps teams design and optimize event-driven architectures to coordinate flows across SomosTecnicos' admin, customer, and technician portals, reducing integration friction and enabling real-time responsiveness.

Core Features & Use Cases

  • Design and validated event schemas and contracts for cross-portal communications.
  • Define orchestration patterns (sagas, compensations) to manage long-running processes.
  • Ensure reliability with idempotency, error handling, and observability across portals.

Quick Start

Outline an initial event-flow diagram for an order lifecycle spanning admin, customer, and technician portals.

Frequently Asked Questions about eda-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design event-driven architecture for cross-portal workflows?▼

Event-driven architecture for cross-portal workflows is designed by defining event schemas, orchestrating saga patterns, and enforcing fault tolerance to coordinate real-time flows across admin, customer, and technician portals.

What is the best way to orchestrate long-running processes across multiple portals?▼

Orchestrating long-running processes across multiple portals is best handled using saga patterns and compensations, ensuring reliability through idempotency, error handling, and observability across all event flows.

How do I ensure data consistency in event-driven systems with publish and subscribe?▼

Data consistency in event-driven systems using publish and subscribe is ensured by enforcing event contracts, supporting event sourcing, and providing guardrails for safe schema evolution.

Can I use saga patterns to handle fault tolerance and error handling in distributed systems?▼

Saga patterns handle fault tolerance and error handling in distributed systems by defining compensation logic and enforcing idempotency, which maintains reliable state across cross-portal event workflows.

When should I use event sourcing for cross-portal communications?▼

Event sourcing for cross-portal communications should be used to capture state changes as a sequence of events, enabling real-time responsiveness while enforcing event contracts and idempotency.

Related Skills

Explore More Software Engineering Skills→
FernanSuozaFernanSuoza

arch-api-contract-designer

Design API and event contracts with OpenAPI and JSON Schema specifications.

Community
Advanced
DexploarerDexploarer
7

event-driven-architect

Architect event-driven microservices with event sourcing, CQRS, and saga patterns.

Community
Advanced
alti3alti3
7

litestar-channels

Configure publish-subscribe channels for real-time event delivery in Litestar applications.

Community
Advanced
FlexNetOSFlexNetOS

Messaging & Event Systems

Coordinate NATS pub/sub and Temporal workflows for distributed messaging.

Community
Advanced