How does event sourcing handle the requirement for data no longer be in the database at all, e.g. if a user asks deleting all his data that ever existed?
One of the best and safest methods in an immutable event store is to store sensitive data as a reference. Some purpose-built event stores offer such capabilities by design.
(I'm asking because it's super annoying that some pseudo-smart people come up with an oh-so-clever approach of "look ma, I have detected AI slop" over and over again, when all they actually do is piss people off who write by hand.)
How does event sourcing handle the requirement for data no longer be in the database at all, e.g. if a user asks deleting all his data that ever existed?
One of the best and safest methods in an immutable event store is to store sensitive data as a reference. Some purpose-built event stores offer such capabilities by design.
There are a number of strategies, some described here: https://docs.eventsourcingdb.io/best-practices/gdpr-complian...
Was this mostly AI written?
No. Was your comment AI-written?
(I'm asking because it's super annoying that some pseudo-smart people come up with an oh-so-clever approach of "look ma, I have detected AI slop" over and over again, when all they actually do is piss people off who write by hand.)