Yash
    04 / 05·Active·All case studies

    PromptP

    Realtime event-driven workflows for creator tooling.

    GitHub
    PromptP — project preview

    Overview

    PromptP is a realtime event-driven platform exploring low-latency synchronization and creator-focused workflow systems.

    The architecture is centered around append-only event logs, Redis Streams, reconnect-safe cursor protocols, optimistic UI updates, and realtime fanout handling.

    The project focuses more on systems behavior and event durability than traditional content-platform features.

    Problem

    Most realtime creator tools fail under reconnect scenarios, slow consumers, or burst fanout traffic.

    A lot of systems tightly couple state mutation and transport layers, which makes debugging synchronization issues difficult.

    The goal was to build a predictable event-driven architecture with durable event history and reconnect-safe recovery flows.

    Architecture

    Backend systems use Node.js, Redis Streams, append-only event logs, WebSockets, reconnect cursors, and event bus coordination.

    Frontend systems are built with React and realtime optimistic UI patterns.

    Backpressure handling exists at the socket layer to prevent slow clients from blocking broader fanout operations.

    Write

    1. ClientOptimistic update, applied locally
    2. WebSocket serverNode.js
    3. Redis StreamAppend-only log; the ID is the order

    Fanout and resume

    1. Stream readerReads from the last delivered ID
    2. Per-socket bufferBackpressure for slow clients
    3. ClientsKeep a cursor; resume after it on reconnect
    The log is the source of truth, so a dropped connection costs a replay, never an event.

    Tradeoffs

    The system prioritizes transport correctness and reconnect reliability over large feature breadth.

    Certain advanced collaborative systems and marketplace functionality were intentionally deferred to keep the event model maintainable.

    Append-only
    Event log
    Cursor
    Resume
    Redis Streams
    Coordination

    What I'd do differently

    The project improved understanding of event-driven architecture, reconnect-safe synchronization, optimistic state handling, and transport-level backpressure.

    It also reinforced how important durable event history becomes once realtime coordination is introduced.

    Writing about PromptP