You'd still need to decrypt the whole table to do e.g. aggregation.
For example, a customer's address is private information; statistics about how many customers come from each town/region is not, but calculating a simple "select town, count(*) from x group by town" requires decrypting every address.
you can store whatever you want unencrypted on the read model. That‘s the place where you do joins/aggregation anyway.
Re:Kafka, GDPR and Event Sourcing
by DelightOne on Friday April 13, 2018 @07:38AM
(#16828991)
> you can store whatever you want unencrypted on the read model.
So to recap correct me if I’m wrong:
You store everything encrypted.
You have an api on it which hides the encryption and shows everything unencrypted.
On the unencrypted api you do joins/aggregations.
RightToBeForgotten then means delete its decryption key and remove it from the in-memory api.
Right?
Data for a join, ie foreign keys, are used to inform your structure. They aren’t really data a person owns... they just describe how that data (theirs) fits into your database (yours).