Re:Deleting data distributed throughout a microservice archi...
by gravypod on Wednesday May 06, 2020 @12:57AM
(#23088021)
It's also possible to completely automate this. Flow.io has a great talk where the CTO talks about everything they do from an engineering perspective. Just annotate data in your API spec language as PII. This can allow you to also have policies that can be verified by this. If some advice has PII you can enforce that some other service can never talk to it, for example.
Re:Deleting data distributed throughout a microservice archi...
by 616c on Wednesday May 06, 2020 @03:23AM
(#23088641)
Link? I would love to see this as excuses not to do so come up often at work, sigh.
Re:Deleting data distributed throughout a microservice archi...
by mcintyre1994 on Wednesday May 06, 2020 @06:46AM
(#23089542)
I'm pretty sure they're referring to this talk: https://www.youtube.com/watch?v=j6ow-UemzBc
Microservices do not get you out of having to have an information architecture. They add more friction if you don't have one, but it's entirely possible to have an unspoken/undocumented information architecture that mostly works.
If you don't have a System of Record for data, you for sure aren't going to be able to find it. Similar problem with no Source of Truth. For some business models you will have both and they will be separate (especially with 3rd party data).
You still have the problem of logs, but at least the problem is tenable. Without any of this it's just chaos and who knows where the data went or really even where it came from?