Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...


Page Properties


Status

Status
colourBlue
titleAccepted

Impact

Status
titlelow

Prod Ticket

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4305

Arch Ticket

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyARCH-148


Executive Summary

LoC requires an authority deletion feature. The implementation should not have a negative impact on active records performance.

...

  • Same tablespace as the active table. Table name pattern <original_table_name>_archive 
  • Trigger on delete should be implemented to move the record to the archive table.
  • Domain events should be distinct for soft- and hard-delete.
  • Update lastUpdatedDate, updatedByUserId in metadata.
  • Tenant-level retention policy should be provided through configuration parameters.

...

  • Soft-delete:
    1. update the soft-delete flag in the original table, send events
    2. after events are processed, move the deleted record to the archive table
  • Hard-delete:
    • if the retention policy is set then, on schedule the archive table should be cleaned by lastUpdatedDate field
    • if the retention policy for the tenant is set to never then no clean up is required

Open Questions

#QuestionAnswer
1

Do we have to implement an "undo" action for delete(restore record)?

2Are performance requirements numbers for peak moments or is every week expected to have such a load?