ро́бот ве́ртер

verter is a curator of institute of time.
his most famous adventure takes place in the year of 2084..

what and why
how to play
adding facts
- don't record what is already known
looking at facts
add data store
transactions
useless benchmarks
- writes
- reads
license

what and why

verter is not a database, it is not a data store
it relies on one though to manage records about identities in space and time.

in contrast to crux, datomic and other temporal databases the idea behind verter is not to be your database, but to live "inside" an existing database to provide audit, history and other bitemporal human needs.

verter is influenced by work that is done by the crux team. if a bitemporal solution is what you are after, where all the data can live in crux, you should just start using crux instead. verter is for use cases where you already have a database / data store.

how to play

since verter sits inside the existing database all it needs is a datasource, which could be an existing datasource, or a new one to, for example, have a separate connection pool. but do start from the datasource you already have.

create a datasource

this example is using a datasource to Postgres:

=> (require '[hikari-cp.core :as hk])
=> (def db (hk/make-datasource {:adapter "postgresql" :url "..."})))

until now there is nothing verter specific, we just creating a datasource. check out a working example in dev.clj.

allow verter in

=> (require '[verter.core :as v]
            '[verter.store :as vs])

=> (def verter (vs/connect :postgres db))

regardless of which data store verter is connected to API will behave the same way
hence, if it is easier, you can connect with SQLite, then come back here and follow the API examples

create institute of time

in case this is the first time verter is used with this database, the institute of time (verter tables/buckets) need to be created:

=> (vs/create-institute-of-time :postgres db)

in case you need to create it in a particular database schema you can do it as well:

=> (vs/create-institute-of-time :postgres db {:schema "foo_bar"})

adding facts

=> (v/add-facts verter [{:verter/id :universe/one :suns 12 :planets #{:one :two :three}}
                        [{:verter/id :universe/two :suns 3 :life? true} #inst "2019-09-09"]
                        {:verter/id :universe/sixty-six :answer 42}])

{:tx-id #uuid "5f62d4c0-c5ca-4431-ac33-610825f9ef36"}

there are a few things to mention here:

every identity needs to have a :verter/id
facts about :universe/two were given a "business time"
other facts will assume that their business time is the transaction time
all these facts were recorded in a single transaction
this transaction id ("tx-id") is 5f62d4c0-c5ca-4431-ac33-610825f9ef36

don't record what is already known

let's try this again:

=> (v/add-facts verter [[{:verter/id :universe/two :suns 3 :life? true} #inst "2019-09-09"]])

{:noop "no changes to identities were detected, and hence, these facts
        [[{:verter/id :universe/two, :suns 3, :life? true} #inst \"2019-09-09T00:00:00.000-00:00\"]]
        were NOT added at 2020-09-17T03:16:58.774118Z"}

since we already know this fact about :universe/two at this business time.

but.., let's update the business time of this, same, fact about :universe/two:

=> (v/add-facts verter [[{:verter/id :universe/two :suns 3 :life? true} #inst "2020-09-09"]])

{:tx-id #uuid "5f62d5af-c4e1-475d-b086-3dad13015623"}

even if we did not provide an "time" at all the fact would be recorded
since the "transaction time" will be used instead (which does change.. one planck at a time):

=> (v/add-facts verter [{:verter/id :universe/two :suns 3 :life? true}])
{:tx-id #uuid "5f62d6b3-df46-4d76-9b71-d8bc3619d791"}

you might have noticed that transaction ids are sequential UUIDs. good catch!

looking at facts

=> (v/facts verter :universe/sixty-six)

[{:answer 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}]

facts function will return all the changes to an identity over time:

let's add more suns to :universe/one:

=> (v/add-facts verter [[{:verter/id :universe/one :suns 42}]])

{:tx-id #uuid "5f62d75d-af6e-4a1d-8687-fc1ee690d1f4"}

and look at how universe was doing its magic by adding more suns over time:

=> (v/facts verter :universe/one)

[{:suns 12,
  :planets #{:one :three :two},
  :verter/id :universe/one,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}
 {:suns 42,
  :verter/id :universe/one,
  :at #inst "2020-09-17T03:26:21.253047000-00:00"}]

"facts" would also show "business time" changes:

=> (v/facts verter :universe/two)

[{:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2019-09-09T00:00:00.000000000-00:00"}
 {:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-09T00:00:00.000000000-00:00"}
 {:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-17T03:23:31.132664000-00:00"}]

i.e. 👆 no facts were really changed, but there was a change in "business time" that we did earlier.

ah, yes ":at" is da "business time". good catch!

with transaction intel

you may add {:with-tx? true} to see the transaction intel across history:

=> (v/facts verter :universe/two {:with-tx? true})

[{:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2019-09-09T00:00:00.000000000-00:00",
  :tx-time #inst "2020-09-17T03:15:12.859748000-00:00",
  :tx-id #uuid "5f62d4c0-c5ca-4431-ac33-610825f9ef36"}
 {:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-09T00:00:00.000000000-00:00",
  :tx-time #inst "2020-09-17T03:19:11.341449000-00:00",
  :tx-id #uuid "5f62d5af-c4e1-475d-b086-3dad13015623"}
 {:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-17T03:23:31.132664000-00:00",
  :tx-time #inst "2020-09-17T03:23:31.132664000-00:00",
  :tx-id #uuid "5f62d6b3-df46-4d76-9b71-d8bc3619d791"}]

facts upto

let's add some more facts about the :universe/sixty-six:

=> (v/add-facts verter [{:verter/id :universe/sixty-six :suns 42 :planets #{:and-all :earth}, :life? true}
                        {:verter/id :universe/sixty-six :moons 42}
                        {:verter/id :universe/sixty-six :moons nil}])

{:tx-id #uuid "5f62d86d-b7ac-4821-ad65-70ced2f5e95a"}

so now it looks like this:

=> (v/facts verter :universe/sixty-six)

[{:answer 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}
 {:suns 42,
  :planets #{:and-all :earth},
  :life? true,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons nil,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}]

when looking for facts we can specify a certain time upto which the facts are needed:

=> (v/facts verter
            :universe/sixty-six
            {:upto #inst "2020-09-17T03:20:00"})

[{:answer 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}]

since the other 3 facts were added a bit after "2020-09-17T03:20:00", there is only one fact that "matters" in this case.

identity now

continuing with :universe/sixty-six with currently 4 facts:

[{:answer 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}
 {:suns 42,
  :planets #{:and-all :earth},
  :life? true,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons nil,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}]

a quite frequent need is to see the identity "now": i.e. all the facts rolled up over time.

this can be done with a rollup function:

=> (v/rollup verter :universe/sixty-six)

{:answer 42,
 :verter/id :universe/sixty-six,
 :at #inst "2020-09-17T03:30:53.388072000-00:00",
 :suns 42,
 :planets #{:and-all :earth},
 :life? true}

one interesting "fact" about this rollup example: the moons.
the last fact about the moons is that it is "nil", hence while it still shows up in the list of facts, unless it has a value, it won't show up in a rollup.

identity "as of"

similarly to the "identity now" rollup above, we can look at an identity at a given point in time a.k.a. "as of" time:

let's add a fact about the moons right before that transaction with 3 facts above:

=> (v/add-facts verter [[{:verter/id :universe/sixty-six :moons 13} #inst "2020-09-17T03:20:00"]])

{:tx-id #uuid "5f62de48-14c9-4acb-99d6-82e721d50443"}

now :universe/sixty-six looks like this:

=> (v/facts verter :universe/sixty-six)

[{:answer 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:15:12.859748000-00:00"}
 {:moons 13,                                         ;; here is out "new" moon count
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:20:00.000000000-00:00"}   ;; with its own busines time
 {:suns 42,
  :planets #{:and-all :earth},
  :life? true,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons 42,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}
 {:moons nil,
  :verter/id :universe/sixty-six,
  :at #inst "2020-09-17T03:30:53.388072000-00:00"}]

see that second fact about the number of moons, but with the earlier business time 03:20 vs. 03:30?

let's look at this identity (:universe/sixty-six) upto this business time:

=> (v/as-of verter :universe/sixty-six #inst "2020-09-17T03:20:00")

{:answer 42,
 :verter/id :universe/sixty-six,
 :at #inst "2020-09-17T03:20:00.000000000-00:00",
 :moons 13}

as of "2020-09-17T03:20:00" this universe had 13 moons and the answer was and still is.. 42.

add data store

supported data stores:

data store	supported	in progress
PostgreSQL	✅
SQLite	✅
MySQL
Redis
Cassandra
Couchbase
MsSQL
Oracle
Your store

❤️ consider contributing to add a support for a data store that is used by your applications.

adding a missing data store comes down to 1, 2, 3

implement `Identity` protocol

(defprotocol Identity
  (facts [this id]
         [this id opts]
    "find all the facts about the identity until now or with options")

  (add-facts [this facts]
    "add one or more facts with or without time specified
     if time is not specified, a single transaction time is used")

  (obliterate [this id]
     "'big brother' move: the idenitity never existed"))

take a look at postgres or, say, sqlite implementations to get an idea.

add a `connect` function

take a look at postgres or sqlite connect function.

the idea is to take a datasource of an existing data store and create an instance of the Identity protocol above.

create schema

depending on what a data store is you might (or not) need to create a schema where verter will keep facts about identities and transactions. i.e. make a function that will create a schema.

of course redis "schema" would probably be just a couple of bucket names vs. a SQL database schema would need to create a couple of tables.

take a look at the postgres schema or sqlite schema to get an idea.

if you are interested and/or need more details, just open an issue, and let's talk

SQLite

here is an example of using verter with a SQLite database:

=> (require '[verter.core :as v]
            '[verter.store :as vs]
            '[hikari-cp.core :as hk])

=> (def db (hk/make-datasource {:jdbc-url "jdbc:sqlite:/tmp/multi-universe.db"}))
=> (def verter (vs/connect :sqlite db))

if it is the first time connecting to this database, we need to create a schema:

=> (vs/create-institute-of-time :sqlite db)

ready to rock:

=> (v/add-facts verter [{:verter/id :universe/one :suns 12 :planets #{:one :two :three}}
                        [{:verter/id :universe/two :suns 3 :life? true} #inst "2019-09-09"]
                        {:verter/id :universe/sixty-six :answer 42}])

=> (v/add-facts verter [{:verter/id :universe/one :suns 42 :planets #{:one :two :three}}
                        [{:verter/id :universe/two :suns 3 :life? true} #inst "2020-09-09"]
                        {:verter/id :universe/sixty-six :answer 42}])

=> (v/facts verter :universe/one)

[{:suns 12,
  :planets #{:one :three :two},
  :verter/id :universe/one,
  :at #inst "2020-09-15T18:33:23.736-00:00"}
 {:suns 42,
  :planets #{:one :three :two},
  :verter/id :universe/one,
  :at #inst "2020-09-15T18:33:42.035-00:00"}]

and here is what's brewing inside the database:

$ sqlite3 dev/verter.db

sqlite> select * from facts;

1|:universe/one|NPY|6f19337c3663044aeebe621321fed52a
2|:universe/two|NPY|82f5ff2d5d5f61d8175b029b37036704
3|:universe/sixty-six|NPY|fc303f3a3088da2eef9b706ed7de8a06
4|:universe/one|NPY|1719aa1d06b9405a1c4a970d99d2c4fd

sqlite> select * from transactions;

5f62e625-4bef-45a0-af73-2f3eefd22f96|6f19337c3663044aeebe621321fed52a|1600316965087|1600316965087
5f62e625-4bef-45a0-af73-2f3eefd22f96|82f5ff2d5d5f61d8175b029b37036704|1567987200000|1600316965087
5f62e625-4bef-45a0-af73-2f3eefd22f96|fc303f3a3088da2eef9b706ed7de8a06|1600316965087|1600316965087
5f62e637-5f71-4c16-8501-931c79fc6e29|1719aa1d06b9405a1c4a970d99d2c4fd|1600316983411|1600316983411
5f62e637-5f71-4c16-8501-931c79fc6e29|82f5ff2d5d5f61d8175b029b37036704|1599609600000|1600316983411
5f62e637-5f71-4c16-8501-931c79fc6e29|fc303f3a3088da2eef9b706ed7de8a06|1600316983411|1600316983411

transactions

by default verter stores facts and its metadata within a database transaction, if a backing store (postgresql, sqlite, etc.) supports such transactions of course.

in cases when facts are recorded as part of an existing (outer) database transaction, in order to avoid nesting transactions, verter can be wrapped into the within-tx function:

=> (vs/within-tx verter tx)

which tells verter it runs within an existing/outer transaction, and there is no need for an internal/default one.

for example, if a JDBC store is used:

=> (jdbc/with-transaction [tx db {:read-only false}]
    (let [vt (vs/within-tx verter tx)]
      (v/add-facts vt [{:verter/id :universe/one :suns 42 :planets #{:one :two :three}}])))

useless benchmarks

since most of the work is done directly against the database, let's pretend the asking party is collocated with such database:

these are the numbers on top of Postgres:

writes

we'll create 40,000 "double" facts (about suns and moons) and partition them in 80 batches 500 entries each:

=> (def universe-42 (partition 500
                      (mapcat #(vector {:verter/id :universe/forty-two :moons % :suns %})
                                       (range 40000))))
#'dev/universe-42

and add them to verter:

=> (time (doall (pmap (partial v/add-facts verter) universe-42)))
"Elapsed time: 1089.960547 msecs"

that's about 40,000 a second.

but of course the postgres is local in this bench which would usually not be the case.

later we'll play with type hints, threads, better batch sizes would also help..
but the most time will always be in I/O, so this is close.

reads

let's read facts for :universe/two that has four entries and looks like this:

=> (v/facts verter :universe/two)
[{:suns 42,
  :moons nil,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-10T22:33:20.204008000-00:00"}
 {:suns 42,
  :moons 12,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-10T22:10:36.352157000-00:00"}
 {:suns 42,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2020-09-10T22:10:22.712308000-00:00"}
 {:suns 3,
  :life? true,
  :verter/id :universe/two,
  :at #inst "2019-09-09T00:00:00.000000000-00:00"}]

=> (time (dotimes [_ 6500] (v/facts verter :universe/two)))
"Elapsed time: 1072.743808 msecs"

these benchmarks are "entertainment" hence no "criterium", multiple threads, connection pool tricks, light speed network latency, etc..

license

Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.

Name		Name	Last commit message	Last commit date
Latest commit History 78 Commits
dev		dev
doc/img		doc/img
resources/verter/store		resources/verter/store
src/verter		src/verter
test		test
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
Makefile		Makefile
README.md		README.md
deps.edn		deps.edn
pom.xml		pom.xml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

ро́бот ве́ртер

what and why

how to play

create a datasource

allow verter in

create institute of time

adding facts

don't record what is already known

looking at facts

with transaction intel

facts upto

identity now

identity "as of"

add data store

implement `Identity` protocol

add a `connect` function

create schema

SQLite

transactions

useless benchmarks

writes

reads

license

About

Releases

Packages

Contributors 4

Languages

tolitius/verter

Folders and files

Latest commit

History

Repository files navigation

ро́бот ве́ртер

what and why

how to play

create a datasource

allow verter in

create institute of time

adding facts

don't record what is already known

looking at facts

with transaction intel

facts upto

identity now

identity "as of"

add data store

implement Identity protocol

add a connect function

create schema

SQLite

transactions

useless benchmarks

writes

reads

license

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Contributors 4

Languages

implement `Identity` protocol

add a `connect` function

Packages