3 ms·
So is this something I would want to use for a basic CRUD application, and reap the benefits of time travel and immutability? Or are there downsides that would
by nerdponx 5y ago
So is this something I would want to use for a basic CRUD application, and reap the benefits of time travel and immutability?
Or are there downsides that would relegate it to specific use cases? A what would those use cases be?
- brokencube 5y agoIt wouldn't be suitable for any application where you care about GDPR (i.e. you store personal information and have users in the EU) The "right to be forgotten" is not compatible with immutable data. You can't simply need to mark data as deleted, you need to 'purge' it from your system (and possible backups, depending on how long you keep historic backups) - that isn't possible in a system with immutable data.
- blablabla123 5y agoI mean there are solutions for this. About CQRS/Event sourcing I've read that it's possible to solve it by encrypting the data with different keys and then rotating/throwing away the keys every now and then. Seems a bit hacky but probably there are more elegant approaches.