system-type-real-time

Design and evaluate real-time collaborative systems with connection and synchronization patterns.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/microsoft/amplifier-bundle-systems-design --skill system-type-real-time
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-type-real-time
Source: https://github.com/microsoft/amplifier-bundle-systems-design/tree/main/skills/system-type-real-time
Command: npx skills add https://github.com/microsoft/amplifier-bundle-systems-design --skill system-type-real-time

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing and evaluating real-time and collaborative systems, providing patterns and strategies for persistent connections, state synchronization, and conflict resolution.

Core Features & Use Cases

  • Connection Patterns: Explains WebSocket, SSE, Long Polling, and WebTransport, guiding implementation for chat, gaming, and live data dashboards.
  • State Synchronization: Offers methods like server-authoritative state, optimistic updates, CRDTs, and operational transformation, for consistent multi-user experiences.
  • Reconnection & Scaling: Provides strategies for reconnect, offline queue management, fan-out, backpressure, and scaling persistent connections to handle massive user loads.
  • Use Case: Ideal for building real-time collaborative editors, multiplayer gaming backends, or live trading dashboards requiring low latency and high consistency.

Quick Start

Use this Skill to implement persistent, low-latency communication in a collaborative web app, ensuring robust reconnection and conflict management.

Frequently Asked Questions about system-type-real-time

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

FAQPage Schema
How do I handle state synchronization and conflict resolution in a real-time collaborative editor?

State synchronization and conflict resolution in a real-time collaborative editor can be handled using server-authoritative state, optimistic updates, CRDTs, or operational transformation to ensure a consistent multi-user experience.

What is the best way to scale WebSocket connections for massive multiplayer gaming backends?

Scaling WebSocket connections for massive multiplayer gaming backends involves implementing fan-out, backpressure management, and offline queue strategies to handle persistent connections and massive user loads resiliently.

How does CRDT compare to operational transformation for real-time collaboration?

CRDTs and operational transformation are both methods for state synchronization in real-time collaboration. CRDTs enable decentralized conflict resolution, while operational transformation typically requires a server-authoritative state to manage consistent multi-user edits.

When do I need WebTransport or SSE instead of WebSocket for live data dashboards?

You need WebTransport, SSE, or WebSocket for live data dashboards based on your connection requirements. SSE is ideal for simple server pushes, WebTransport offers low-latency bidirectional streams, and WebSockets provide persistent bidirectional communication.

How do I implement robust reconnection and offline queue management for real-time chat applications?

Robust reconnection and offline queue management for real-time chat applications are implemented using specific connection lifecycle strategies that handle backpressure, mitigate failures, and queue messages during network interruptions.

Does this approach support offline updates and backpressure for low-latency trading dashboards?

Yes, this approach supports offline updates and backpressure for low-latency trading dashboards by utilizing optimistic updates and backpressure strategies to maintain high consistency and resilient data flow during network constraints.