real-time-architect

Design real-time architecture for WebSocket, SSE, and WebRTC systems.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill real-time-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: real-time-architect
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/real-time-architect
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill real-time-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Real-time systems are hard to design at scale; this Skill provides a clear blueprint for architecting low-latency, high-throughput real-time applications across WebSocket, SSE, and WebRTC, including patterns, trade-offs, and guardrails.

Core Features & Use Cases

  • Comprehensive real-time architecture guidance for chat, collaboration, gaming, and streaming.
  • Pattern catalog (Direct, Gateway, Edge, Managed) and transport choices with trade-offs.
  • Non-functional requirements checklist: reconnection, ordering guarantees, backpressure, observability, and security considerations.

Quick Start

Provide an initial architecture plan for a real-time application given latency and scale targets.

Frequently Asked Questions about real-time-architect

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

FAQPage Schema
How do I design a scalable real-time WebSocket architecture for high fan-out applications?

Scalable real-time WebSocket architecture uses Gateway or Edge patterns to manage high fan-out, ensuring low latency and throughput for chat, collaboration, or gaming contexts.

What is the best way to choose between WebSocket, SSE, and WebRTC for low-latency systems?

Transport selection depends on your use case: WebRTC suits peer-to-peer gaming, SSE fits one-way streaming, and WebSocket handles bidirectional chat, with trade-offs in latency and state synchronization.

How do I handle state synchronization and CRDTs in real-time collaboration apps?

State synchronization in real-time collaboration uses approaches like CRDTs to manage concurrent updates, ensuring data consistency across clients while maintaining low latency and ordering guarantees.

What non-functional requirements are critical for real-time architecture design?

Critical non-functional requirements for real-time architecture include reconnection strategies, message ordering guarantees, backpressure management, observability, and security considerations to ensure system stability.

When should I use Edge versus Managed real-time architecture patterns?

Use Edge patterns to minimize latency by processing data closer to users, while Managed patterns offload infrastructure complexity, with trade-offs involving control, scalability, and operational overhead.

Why does my real-time streaming application suffer from high latency and message ordering issues?

High latency and ordering issues in real-time streaming often stem from lacking backpressure management and ordering guarantees, requiring architecture patterns that enforce strict message sequencing and flow control.