we too have authorization rules at the boundary, all commands and queries from clients are authorized… I think it’s common that authorization is based on a few core entities that are part of the query args / command payload
Q: about creating a global datomic cloud service i.e. multi-regions. does anyone have experience with this? https://forum.datomic.com/t/replication-of-some-all-datoms-to-other-dbs/1779
Hey @steveb8n sorry I missed the post. I just updated on the forum thread as slack gets archived. I am just hoping to understand the problem space a little bit better before I jump into cross region advice/approaches.
@jaret thanks. I’ve replied there too. better for it to be in a permanent record for others.
that nubank presentation with filter was interesting, it would be to see actual performance numbers… it would seem to me that the filter approach can’t use indexes efficiently, but don’t know any details
Understanding question: If you pull an existing attribute (that isn’t :db/id
) of a non-existing entity, you get nil
, but if you pull :db/id
of that same non-existing entity, you get {:db/id nil}
. Why is that?