Home / Product / Realtime events

Make experiences live

Keep screens current as the product changes.

Publish live create, update, and delete events so permitted clients can react without repeatedly asking whether something changed.

See what it changes Technical guide ↗

Realtime events in a product

Something changesA record is created, updated, or removed

The backend publishes the eventUse a live topic tied to application context

Connected screens respondRefresh the view or start the next experience

Committed changes can become visible now

01Reduce stale screensTell connected clients when relevant data changes.

02Build reactive experiencesUpdate dashboards, queues, and status views as work happens.

03Keep live delivery connected to accessUse authenticated, permission-aware topics.

Why it matters

A shared product feels broken when every person sees a different moment.

A teammate assigns a task, an operator resolves a request, or a customer uploads a document. Without live updates, other screens remain stale until someone refreshes or the client polls again.

Daptin publishes events after successful record changes and exposes live topics over WebSockets. Compatible multi-node deployments distribute that fanout through the shared runtime.

The event tells the client that something changed; the ordinary resource API remains the source for current durable data. This keeps live experience and stored truth in their appropriate roles.

Make change visible quickly

React to new, updated, or removed records while people are using the product.

Avoid constant polling

Keep a connection for relevant events rather than repeating list requests.

Connect live behavior to the model

Use the same record and identity context as the rest of the backend.

How it fits

Part of one connected backend.

Realtime events does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Change

A permitted operation commits a record update.

Step 2Publish

The runtime sends the relevant event to its live topic.

Step 3Authorize

The connection and subscription follow the supported access rules.

Step 4Refresh

The client updates the experience or reads the latest record.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Live work queue

Show new and reassigned requests to the right operations team.

Status tracking

Update a customer-facing progress view when work advances.

Collaborative dashboard

Keep totals and recent activity current across several viewers.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes realtime events more useful.

Know the boundary

What Daptin leaves in your hands.

Realtime events are live fanout, not a durable event log. Disconnected or slow clients can miss delivery and should reload durable state. Capacity-test connection counts, fanout, and multi-node behavior.

Understand the operating responsibility →

Build from one foundation

Make realtime events part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities