31–40 of 48 posts
This will be a tongue in cheek comment, but there's another thing Datomic isn't making you do either: GDPR compliance
It's a bit of an existential point, but if your logic allows the disclusion of data before a certain point of time, is that not effectively the same as not possessing it?
This will be a tongue in cheek comment, but there's another thing Datomic isn't making you do either: GDPR compliance
Well, they do support extinctions?
Immutable is only immutable if you don't have write access to the lowest layer of storage.
One thing though: you still have to do data modeling. No matter how much you pretend that you don't have to do it, you still need relationships, and unique references, getting and querying ranges. Hell, even data access restrictions.
Delaying data architecture decisions is usually better than attempting to plan for them up front.
Earlier quoted context omitted.
OP here :) True, in that there's no solution out of the box. I kind of want to make a "look at all the things I have to do", and GDPR compliance is one of those things where there are probably many ways to do it wrong with Datomic, and a few ways of doing it right. One thing you can do, is to have a separate database for each person/user. It is trivial to join across multiple databases in Datomic, and you can even do…
IANAL, but I‘m pretty sure it is acceptable to delete data within 30 days of receiving a request to do so.
This will be a tongue in cheek comment, but there's another thing Datomic isn't making you do either: GDPR compliance
Well, they do support extinctions?
One thing though: you still have to do data modeling. No matter how much you pretend that you don't have to do it, you still need relationships, and unique references, getting and querying ranges. Hell, even data access restrictions.
But quite often your first two or five models will be wrong. Usually the exact problem is not clear early on... Delaying data architecture decisions is usually better than attempting to plan for them up front.
For those that don't know, Datomic is a hosted database, similar to how Clojure is hosted. Datomic can be hosted on MySQL or PostgreSQL (and maybe others?). It's basically a 2 column table, so yes, Datomic inherits transaction safety. According to people I know that use Datomic, an early lesson is indexing, which apparently is often done way later than it should. Datomic also inherits the speed of indexing a huge tab…
What do you refer to when you say that Datomic inherits the speed of indexing a huge table? The query engine works by fetching blocks of data from storage and placing the blocks in a lazy immutable tree structure that are the indices of Datomic. They are also covering (the indices is where the actual data is stored). So it's not like the query engine runs queries on the huge table stored in mysql or postgres, it's used more like a key/value store. Case in point: you can put memcached between the datomic client (peer) and any of the supported storage engines. So Datomic piggybacks on very little other than the actual capabiliy to safely store data.
Earlier quoted context omitted.
Well, they do support extinctions?
That is certainly something an add-on or external tool could provide. Immutable is only immutable if you don't have write access to the lowest layer of storage.
Earlier quoted context omitted.
But quite often your first two or five models will be wrong. Usually the exact problem is not clear early on... Delaying data architecture decisions is usually better than attempting to plan for them up front.
I whole heartedly disagree. Data doesn't care about your application.
On the other hand, I have worked with people who like to try to plan for all possibilities. That usually results in enormous data models and extra layers of abstraction that never prove their value.
For those that don't know, Datomic is a hosted database, similar to how Clojure is hosted. Datomic can be hosted on MySQL or PostgreSQL (and maybe others?). It's basically a 2 column table, so yes, Datomic inherits transaction safety. According to people I know that use Datomic, an early lesson is indexing, which apparently is often done way later than it should. Datomic also inherits the speed of indexing a huge tab…
(0) Every bank account must admit a linear transaction history.
(1) Given a causally related collection of transactions, all involved parties must agree on the relative order of these transactions.
How exactly do you get to enforce invariants like these without transaction coordination?