Data engineering

A clearer view of every order

Bring order updates into one view for operations

The working day, reconsidered.

Orders change throughout the day. Operations needs to see what moved, what stalled, and whether the reporting data is current.

Connecting the pieces.

Send database changes to a separate reporting store, then give the team a dashboard with delivery status and visible data freshness.

Download design brief ↓

Behind the interface

  1. PostgreSQLOrder changes
  2. Debezium + KafkaCapture and buffer updates
  3. PostgreSQLReporting tables
  4. GrafanaOperational view

Decisions that matter

Keep reporting separate

Query a reporting copy so dashboard demand can be managed independently of checkout traffic

Make freshness visible

Show the last processed update and alert when data falls behind the agreed threshold

Plan for replay

Use stable record keys and source offsets to recover from interruptions without duplicating orders

What we’d verify

  • Replay the same event without creating duplicate records
  • Interrupt processing and reconcile recovered records with the source
  • Show a stale-data warning when updates stop

Ready for handover

Code, configuration, operating notes, and knowledge transfer—agreed as part of the scope

See our delivery approach ↗

Bring us your version of the challenge.

We’ll look at the context, the people and the systems together.

Let’s talk