DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 968,547 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in

Discussion on: Kafka, GDPR and Event Sourcing

Collapse
 
kjir profile image
StΓ©phane Bisinger

Although the risk of abuse is quite high, I would personally opt to go around the immutability in this particular instance. Removing it from the projections is probably not enough and the encryption system creates more problems than it solves.

Or, maybe, it's time to see if there could be better options to handle this than Kafka?

Thanks for the interesting read!

Collapse
 
danlebrero profile image
Dan Lebrero Author

For my current context, I am also leaning towards mutability as we are not a big enough team to handle the additional complexity of encryption, but it scares me the potential for abuse.

And yes, maybe Kafka is not the best choice. If you use Java, the Axon framework is going to support something similar out of the box: slideshare.net/Frans_van_Buul/axon...

Cheers!

Dan