Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Exploring four Datomic superpowers

This session will explore four common problems, and the unique and surprising tools Datomic provides to solve them elegantly: HTTP caching - How to generically generate and validate Last-Modified and If-Modified-Since headers Audit trail - how to extend Datomic’s immutable transaction log to include arbitrary audit related metadata Mobile database sync - trivial implementation of an incremental update API for high latency/low bandwidth clients Authorization - easily determine resource ownership, and centrally isolate users from data they are not allowed to see

These problems have certainly been solved before using other databases, but Datomic provides features that make the proposed implementations concise, generic, and purely functional

19.
8
What was the initial limit for the card?
At the time the Starbucks transaction occurred, which
fraud triggers would have activated?

20.
8
What was the initial limit for the card?
At the time the Starbucks transaction occurred, which
fraud triggers would have activated?
How long did the customer spend on each stage of the
acquisition funnel?

21.
8
What was the initial limit for the card?
At the time the Starbucks transaction occurred, which
fraud triggers would have activated?
How long did the customer spend on each stage of the
acquisition funnel?
How frequently do we see amount changes on
Starbucks transactions?

22.
9
What sequence of
events resulted in the
Starbucks transaction
being persisted?