adding-persistent-event

To add a new persistent event, you create the event class, define type aliases, and integrate it with EventLogPayloadTransformer for payload transformation. This ensures the new write operation is properly logged and available for database backfilling if necessary.

Persisting events in a database event log ensures all significant write operations and system changes are permanently tracked. You need persistent events for reliable auditing, debugging, and maintaining an accurate historical record of user data modifications.

The best way to integrate a new event class with EventLogPayloadTransformer is to follow a structured checklist that guides payload transformation setup and database backfilling. This ensures proper event publishing and consistent logging for new write operations.

Yes, you can backfill existing database records when adding a new persistent event. The process involves integrating the new event class with EventLogPayloadTransformer, which supports potential database backfilling to update historical logs with the new event type.

To test new event logging logic, you verify the event class definition, type aliases, and EventLogPayloadTransformer integration. The process includes ensuring proper event publishing and validating that the new persistent event logic accurately records write operations.