CmdrDats

7 ms·

1. 1.▲
   by CmdrDats 11y ago

   Ye, sadly - I tried to make it as browser agnostic as possible, but I had a very tight time schedule for it - but PR's welcome! :D
2. 2.▲
   by CmdrDats 12y ago

   You raise a good point about not being clearer in the project page. I'll give it some thought and probably expand a bit on the dynamodb and datomic sections to incorporate the reasoning. Again though, you are right, the events could be
3. 3.▲
   by CmdrDats 12y ago

   Thanks jamii, that's an excellent read - I forgot to add it to the Further Reading section! Will do that now :)
4. 4.▲
   by CmdrDats 12y ago

   My apologies - my example was to illustrate a fit mismatch, not so much technical deficiencies. Let's try it from a different angle: If you wanted to include every attribute of every event into Datomic as well as the aggregate view, yo
5. 5.▲
   by CmdrDats 12y ago

   So to have a concrete example: in our preliminary test of Datomic, we threw all our page view events directly at Datomic. Every single attribute in the event gets indexed at least 3 times and it grew out of a manageable scale really quick
6. 6.▲
   by CmdrDats 12y ago

   Technically it could - but I felt Datomic is particularly strong as an aggregate view. Adding transactions that just have events attached to them isn't a particularly useful aggregate to query. Having the eventstore separate means that
7. 7.▲
   An Opinionated Clojure CQRS/ES Using Onyx, Datomic, DynamoDB, Kafka(yuppiechef.github.io)

   111 points by CmdrDats 12y ago|33 comments
8. 8.▲
   by CmdrDats 12y ago

   Thanks for this clarification on HMAC - I was also failing to see and understand the relevance to passwords when investigating after watching the talk.