scaffold-delete-operation

Soft-delete in an event-sourced backend API is implemented by creating a tombstoning event, a corresponding delete command, and updating read-model projections to mark the resource as deleted rather than removing it. This preserves audit history and enables recovery.

The best way to scaffold a tombstone event for API resources is to generate a dedicated domain event class, such as a ResourceDeleted event, and wire it to a command handler that updates the aggregate state and read-model projections.

Yes, read-model projections are necessary for soft-delete operations to reflect the deletion state. Projections must handle the deletion event and update the read model, such as setting a Deleted flag to true, ensuring queries recognize tombstoned records.

Yes, you can add a delete endpoint that uses an aggregate-backed handler by updating the API endpoints to support the delete operation with proper state loading, ensuring the aggregate processes the delete command and applies the deletion event.

Soft-delete is preferred over hard delete in domain-driven API endpoints because it preserves audit history and enables data recovery. By tombstoning records through event-sourced patterns, you maintain a complete sequence of domain events.

Soft-delete scaffolding generates a domain event, a delete command, an endpoint update with an aggregate-backed handler, and corresponding read-model updates. This enforces a complete event-sourced workflow for tombstoning resources like Book or Author.