Macroservices - Datomic & the Web from the REPL with Nolan Smith

[@mikl2345]

Regarding the question at the end about GDPR & excision, it seems to me that some projects may need excision to be *possible* , but the *probability* of needing it may be extremely low. Thus, re. lack of excision in datomic cloud, has anyone elaborated a workflow entailing a complete data migration to a new database minus the offending datoms? (like a simple ETL). If that is in fact practical, and even easy(?), then perhaps, for some use cases, the need for separate storage of personal data in some mutable store can simply be skipped? Why pay a big price to make something easy that there's a good chance you may never need?

[@localshred]

One approach I've used is to store data that may need to be excised in a separate datastore from datomic and assert a reference in datomic (external id, hashed value, whatever). When the value needs to be purged from the system it can be removed from the external store (e.g. elasticsearch) and the reference value would be retracted from datomic.

[@JaihindhReddy]

1:03:43 This is the article: hackernoon.com/functional-programming-in-javascript-is-an-antipattern-58526819f21e

[@eduardoraad7378]

Dude looks like Christian Bale