Tracking-service case study: event schemas and non-blocking delivery

The news at the time

In the published transcript, Alina Krasavina describes Delivery Hero’s internal tracking service using mobile and frontend SDKs, an ingestion API, real-time consumers and BigQuery storage. This is the speaker’s implementation account.

The speaker says code-generated event models exposed schema problems during application compilation, while a device queue and background batched sending supported non-blocking delivery. The reported cost and capture-rate figures are excluded from this scoped summary.

Follow-up checked during renewal

No additional follow-up fact was established in this renewal. This does not establish that nothing changed.

What to review before applying this

Treat the transcript as primary evidence of what the speaker reported, not independent replication. Evaluate schema ownership, buffering limits, delivery failures, privacy requirements and migration parity for your own workload.

Editorial review suggestions; no hands-on product experiment was performed.