Real-time data

Kafka event streaming for iGaming: what it is and when you need it

A person in a suit typing on a tablet, with a hologram of a world map, charts, network nodes and envelope icons above it

The short answer

Apache Kafka is a system for moving events from the places that create them to the places that need them, as they happen. An event is a small record that something occurred: a player registered, a deposit completed, a bet settled. Instead of waiting for a nightly file, other systems can react within seconds.

How it works, in four terms

  • Event. One fact, such as a deposit completing, with the details that matter.
  • Topic. A named stream of events of one kind, for example all deposits.
  • Producer. A system that writes events to a topic.
  • Consumer. A system that reads events from a topic, when it is ready.

Producers and consumers do not need to know each other. A new system can start reading a topic without changing the one that writes to it.

Where it helps in iGaming

  • Affiliates. Send registrations and first deposits as they happen, instead of in a nightly file.
  • CRM. Start a journey from what a player just did.
  • Risk and payments. Let your own systems react to a large win or a change in deposit success while it still matters.
  • Compliance applications. Feed real-time compliance tools with the events they consume.
  • Your own applications. Build real-time features from the same stream, with no extra feeds.

When you do not need it

If every consumer is happy with data from yesterday, streaming adds complexity for little gain. Start with a reconciled warehouse and add streaming when a specific use needs speed.

What to plan for

  1. Event names and shape. Keep names consistent across brands and sources, or every integration breaks when one changes.
  2. Enrichment. Adding player, brand and payment context once, at the source, saves every consumer from looking it up.
  3. Repeats and order. Consumers should cope with seeing an event twice, and with events arriving slightly out of order.
  4. Personal data. Decide which fields travel on a stream, and who can read each topic.
  5. Access and audit. Know which partners read which topics, per brand.

How Dejta Broker fits

Dejta Broker is built on Kafka. It sends enriched events in real time to your partners, your tools and your own applications, and takes in events from approved third parties for use across Dejta+. Events come from the same reconciled platform behind Reporting and Studio, with consistent names, scoped to your brands. Dejta Broker is in build, and the event names on our site are examples. See how the platform fits together.

Common questions

Do we need streaming, or are nightly files enough?

Nightly files are enough for monthly reporting. Streaming earns its place when something should respond within seconds or minutes, such as an affiliate report, a CRM journey or a risk check.

Can third parties send events as well as receive them?

Yes, in a well-governed setup. With Dejta Broker, approved third parties can produce events for use across Dejta+, as well as consume them. Dejta Broker is in build.

Talk to us about your data.

Tell us what you run today and what you want to change. We’ll reply within two working days.

Book a demo

  • We’ll reply within two working days.
  • Start with a pilot: the fee is credited against your first invoice if you continue, and your first month is free.

We’ll use these details only to reply to your request, and keep them for seven days.