Realtime communication

When an application should not wait for the next refresh

I design event communication where a user or system should receive information as soon as it occurs.

Discuss a realtime solution →

Polling is not always the answer

Current state without repeated requests to the server

With polling, the browser repeatedly asks whether something changed. A realtime model delivers an event only when it actually occurs.

What realtime can solve

The choice depends on event type, permissions and required reliability.

WebSocket communication

A two-way connection between browser and realtime layer.

Publish / subscribe

Events are delivered only to relevant topics and subscribers.

Monitoring and processing

For dashboards, notifications, CRM, reservations and background processes.

With three robotic AI assistants, I look over an evening city and a diagram connecting applications, backend services and monitoring through a WebSocket broker.
Events should reach the right place at the right time. I design realtime connections that keep systems in sync.

Typical scenarios

  • Live dashboards and monitoring
  • Order, reservation or CRM status
  • Browser user notifications
  • AI and worker processes that publish a result

Technical view

A custom WebSocket broker can be one implementation. Topic routing, namespaces, authorisation and observability are what matter.

PHP backend
     ↓ REST publish
Realtime broker
   ├── Browser
   ├── Worker
   └── AI service

How we work

Event, flow and access control

  1. EventsWhat should be delivered and to whom.
  2. ChannelsTopics, namespaces and access rules.
  3. OperationMonitoring, error states and behaviour verification.

Polling is not always the answer

Current state without repeated requests to the server

With polling, the browser repeatedly asks whether something changed. A realtime model delivers an event only when it actually occurs.

Relevant technologies

GoWebSocketRESTWildcard topicsNamespacesAuthorizationMonitoringDocker

Illustrative example

Immediate event delivery without regular polling

The backend publishes a change; the browser or worker receives only the relevant event.

Backend
  ↓ publish
Broker
  ↓ event
Browser

Should the application react immediately?

Describe the event, users and expected behaviour.

Discuss a realtime solution →