Not all events are created equal

One common type of “driver” in an event-driven application is observations: typically high-volume, ephemeral signals such as measurements, user interactions, telemetry, notifications, and other forms of ”raw” external data. Consider an IoT device management platform consuming MQTT messages that report frequent device updates. If an audit trail is required, it may be tempting to apply Event Sourcing and persist every update. However, this approach turns the event store into a log of what was observed—rather than a record of what was decided. Event Sourcing, by contrast, is intended to capture domain events: immutable facts that represent the outcomes of explicit business decisions. In this webinar, you will gain clear, practical guidance on which events belong in an event-sourced model—and which do not—through concrete, real-world examples built on the Axoniq Platform. We will explore:

• How to distinguish observations from domain events, and how to translate the former into the latter via commands.

• How to populate a data lake with both observations and domain events to support analytics without compromising your system of record.

• How to derive actionable insights and close the feedback loop between analytics and your applications.

This session is designed for technology leaders who want to use Event Sourcing deliberately, not indiscriminately. You’ll learn when Event Sourcing creates real strategic value by modeling and storing what matters - the evolution of your business domain - while integrating observations through a complementary data and analytics pipeline.