keechma/entitydb
EntityDB is a client side database and normalization engine. This is a second iteration of EntityDB, original can be found at https://github.com/keechma/entitydb
Motivation
In apps we're developing, we always work with the incomplete data. Data gets loaded from the server based on the route, and we always load the minimal set required to render the page. Any client side querying and filtering is minimal, and is performed with the functions from the Clojure standard library.
Features we need:
- Normalization - only one instance of an entity should be loaded in memory
- Relationships support - getting related data present in EntityDB (which can be loaded in one or multiple queries to the server)
If your application needs more extensive feature set (like client side querying), something like DataScript might be a better choice.
Usage patterns
When talking about the apps, we usually refer to some datasets by their domain name, like current user, frontpage articles and similar. EntityDB supports storing of these named items and collections which are then resolved by their name. These named items and collections express interest of application in some subset of data. How data gets loaded in EntityDB is up to the developer. Any data that is not linked to some named entity or collection should be considered stale. EntityDB supports vacuuming of stale data - this ensures that you can avoid an accidental memory leak where the data is always accrued, and never removed from the application state.
EntityDB requires minimal or no data transformation before ingestion. We use EntityDB with various backend APIs (GraphQL, REST, Firebase...), and we usually just put whatever is returned from the API inside EntityDB. Usage will be very similar to a system that only uses vectors and maps to store the data - with normalization layer on top.
EntityDB is implemented as a set of pure functions, and it's up to a developer to provide the storage (usually a Clojure atom).
EntityDB allows you to define an optional schema which will be used to extract related entities from any payload that enters the system.
Examples
In this example we'll store and retreive a current user:
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-named {} :user :user/current {:id 1 :username "Retro"}))
(edb/get-named db :user/current) ;; Returns {:id 1 :username "Retro" :entitydb/type :user :entitydb/id 1}
As you can see, we get whatever we put inside (plus some EntityDB attributes). EntityDB doesn't support partial data retrieval - whatever is placed in EntityDB will get returned.
In some cases you'll get parts of entity data from different sources. For instance, you might load a list of articles which will embed some user info, and you could get the whole user entity from a user endpoint. If you put data with the same identity in EntityDB, this data will be merged. Default identity is :id.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-named {} :user :user/current {:id 1 :username "Retro"}))
(def db-1 (edb/insert-named {} :user :user/author {:id 1 :firstName "Mihael" :lastName "Konjevic"}))
(edb/get-named db :user/current) ;; Returns {:id 1 :username "Retro" :firstName "Mihael" :lastName "Konjevic" :entitydb/type :user :entitydb/id 1}
Sometimes, you'll load an entity by id, and you want to put it in EntityDB to ensure that you have the latest data loaded. In that case, you can put an entity directly into EntityDB - without using a named entity. All named entities will be synchronized.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-named {} :user :user/current {:id 1 :username "Retro"}))
(def db-1 (edb/insert-entity {} :user {:id 1 :firstName "Mihael" :lastName "Konjevic"}))
(edb/get-named db :user/current) ;; Returns {:id 1 :username "Retro" :firstName "Mihael" :lastName "Konjevic" :entitydb/type :user :entitydb/id 1}
Named entities' names are contextual. For instance on the URL /article/1, :user/author might point to one entity and on the URL /article/33 it might point to a different one. Other parts of the system (UI) don't have to care about that, and they can always load a named entity by its name.
Removing a named entity will not remove the entity from the store. It will just unlink the name from the entity.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-named {} :user :user/current {:id 1 :username "Retro"}))
(edb/get-named db :user/current) ;; Returns {:id 1 :username "Retro" :entitydb/type :user :entitydb/id 1}
(def db-1 (edb/remove-named {} :user/current))
(edb/get-named db-1 :user/current) ;; Returns nil
(edb/get-entity db-1 :user 1) ;; Returns {:id 1 :username "Retro" :entitydb/type :user :entitydb/id 1}
If you remove an entity from the store, all named entities will be cleaned up automatically.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-named {} :user :user/current {:id 1 :username "Retro"}))
(edb/get-named db :user/current) ;; Returns {:id 1 :username "Retro" :entitydb/type :user :entitydb/id 1}
(def db-1 (edb/remove-entity {} :user 1))
(edb/get-named db-1 :user/current) ;; Returns nil
(edb/get-entity db-1 :user 1) ;; Returns nil
Collections are similar to named entities, but instead of a single entity they point to a vector (or list) of entities. Insertion order is preserved. If you remove an entity from the store it will be removed from any collections too.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-collection {} :user :user/friends [{:id 1 :username "Retro"} {:id 2 :username "TiborKr"}]))
(edb/get-collection db :user/friends) ;; Returns [{:id 1 :username "Retro" :entitydb/id 1 :entitydb/type :user} {:id 2 :username "TiborKr" :entitydb/id 1 :entitydb/type :user}]
(def db-1 (edb/remove-entity db :user 1))
(edb/get-collection db-1 :user/friends) ;; Returns [{:id 2 :username "TiborKr" :entitydb/id 1 :entitydb/type :user}]
(def db-2 (edb/remove-collection db :user/friends))
(edb/get-collection db-2 :user/friends) ;; Returns nil
(edb/get-entity db-2 :user 2) ;; Returns {:id 2 :username "TiborKr" :entitydb/id 1 :entitydb/type :user}
Schema
EntityDB doesn't require a schema before you can start using it. It will happily store the data and return it back. You'll need to define a schema in a few cases:
- You want to change a way the identity is calculated
- You want to define relationships
- You want to define a processor that will be applied to some entities before they enter the system
Example schema
{:note {:entitydb/relations {:links {:entitydb.relation/path [:links :*]
:entitydb.relation/type :link}}}
:link {:entitydb/id :url}}
In this case we're defining schema for two types :note and :link. Link will be using the :url attr as it's identity, and each note will have a relation to multiple links. If you take a look at the way the relation is defined, you'll notice that there is no explicit definition of cardinality. You define a pattern to find where inside the note will links appear. This schema will support note entities that look like this:
{:id 1
:title "Note #1"
:links [{:id 1
:url "http://www.google.com"}
{:id 2
:url "http://www.yahoo.com"}]}
EntityDB will go through each entry in the :links vector and place these maps in the :link store. EntityDB supports relation paths of arbitrary depth - and you can nest vectors and maps in any way you need. This feature was designed in this way to naturally support REST and GraphQL payloads. There is no need to process any nested GraphQL payloads before putting them in EntityDB. Let's take a look at another schema:
{:user {:entitydb/relations
{:urls {:entitydb.relation/path [:urls :*]
:entitydb.relation/type :url}
:authored-posts {:entitydb.relation/path [:authoredPosts :*]
:entitydb.relation/type :post}
:favorite-posts {:entitydb.relation/path [:favoritePosts :edges :* :node]
:entitydb.relation/type :post}
:posts {:entitydb.relation/path [:posts :edges :* :node]
:entitydb.relation/type :post}
:group-members {:entitydb.relation/path [:groups :* :members :edges :* :node]
:entitydb.relation/type :user}
:twitterProfile :twitter-profile
:githubProfile :github-profile}}
:post {:entitydb/id :slug}
:url {:entitydb/id :url}
:twitter-profile {:entitydb/id :username}
:github-profile {:entitydb/id :username
:entitydb/relations
{:repositories {:entitydb.relation/type :github-repository
:entitydb.relation/path [:repositories :edges :* :node]}}}
:github-repository {:entitydb/relations
{[:committers :edges :* :node] :github-profile
:homepage :url}}}
This is closer to something you might write in real application. This is a schema that supports payloads from a GraphQL API that implements a Relay standard. Let's take a look at the :group-members relation of the :user entity type. In this case, path to the group member will require iteration through nested vectors, and then getting the :node attribute from the last level. Support for deep paths allows you to normalize data without needing to write bunch of join entity types. You can focus only on your access patterns, and EntityDB will take care of rest. You also don't have to define a relationship for every nested map or vector, EntityDB will not process them unless you tell it so with the schema. Our goal was to implement a client side DB that requires minimal ceremony.
With that schema defined, we can now insert a payload like this directly in EntityDB (without any preprocessing):
{:username "retro"
:id 1
:posts {:pageInfo {:hasNextPage true}
:edges [{:cursor "1"
:node {:slug "my-post-1"
:title "My Post #1"}}
{:cursor "2"
:node {:slug "my-post-2"
:title "My Post #2"}}]}
:authoredPosts [{:slug "my-post-3"
:title "My Post #3"}]
:favoritePosts {:pageInfo {:hasNextPage true}
:edges [{:cursor "1"
:node {:slug "my-post-3"
:title "My Post #3"}}
{:cursor "2"
:node {:slug "my-post-4"
:title "My Post #4"}}]}
:twitterProfile {:username "mihaelkonjevic"
:tweetCount 1234
:followerCount 123}
:githubProfile {:username "retro"
:repositories {:pageInfo {:hasNextPage false}
:edges [{:cursor "1"
:node {:id 1
:name "keechma"
:homepage {:url "https://keechma.com"
:description "Keechma Homepage"}
:committers {:pageInfo {:hasNextPage false}
:edges [{:cursor 1
:node {:username "retro"}}
{:cursor 2
:node {:username "tiborkr"}}]}}}
{:cursor "2"
:node {:id 2
:name "keechma.entitydb"}}]}}
:urls [{:name "Homepage" :url "https://retroaktive.me"}
{:name "Keechma" :url "https://keechma.com"}]
:groups [{:name "Keechma Developers"
:members {:pageInfo {:hasNextPage false}
:edges [{:cursor 3
:node {:id 1}}]}}]}
The behavior presented previously in this document - merging of entities and cleanup of entities when they are removed from the store is supported for deeply nested payloads.
Schema needs to be inserted in EntityDB before you can start using it:
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-schema {} {:note {:entitydb/relations {:notes {:entitydb.relation/path [:notes :*]
:entitydb.relation/type :note}}}
:link {:entitydb/id :url}}))
Querying relationships
Related entities are not included by default when you get data from EntityDB. They need to be included explicitly.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-schema {} {:note {:entitydb/relations {:links {:entitydb.relation/path [:links :*]
:entitydb.relation/type :link}}}}))
(def db-1 (edb/insert-entity db :note {:id 1
:title "Note #1"
:links [{:id 1
:url "http://www.google.com"}
{:id 2
:url "http://www.yahoo.com"}]}))
(edb/get-entity db-1 :note 1)
;; {:id 1
;; :title "Note #1"
;; :links [(->EntityIdent :link 1)
;; (->EntityIdent :link 2)]
;; :entitydb/id 1
;; :entitydb/type :note}
Getting data from EntityDB without specifying which relations to include returns only idents instead of items.
Include query
You will use the include query most of the time. It is used to include related entities.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
...
(edb/get-entity db-1 :note 1 [(q/include :links)])
;; {:id 1,
;; :title "Note #1",
;; :links
;; [{:id 1,
;; :url "http://www.google.com",
;; :foo "bar",
;; :entitydb/id 1,
;; :entitydb/type :link}
;; {:id 2,
;; :url "http://www.yahoo.com",
;; :foo "baz",
;; :entitydb/id 2,
;; :entitydb/type :link}],
;; :entitydb/id 1,
;; :entitydb/type :note}
Important thing to note here is that include by default resolves only first level of relations but can be extended to
suit your need. For example, if we expand schema from previous example with user relation
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def db (edb/insert-schema {} {:note {:entitydb/relations {:links {:entitydb.relation/path [:links :*]
:entitydb.relation/type :link}}}
:link {:entitydb/relations {:user :user}}}))
// note: defining relation as {:foo :bar} is a shorthand for {:foo {:entitydb.relation/path [:bar] :entitydb.relation/type :bar}}
(def db-1
(-> db
(edb/insert-entity :note {:id 1
:title "Note title"
:links [{:id 1}]})
(edb/insert-entity :user {:id 1
:username "Retro"})
(edb/insert-entity :link {:id 1
:url "http://keechma.com"
:user {:id 1}}))
(edb/get-entity db-1 :note 1 [(q/include :links [(q/include :user)])])
;; {:id 1,
;; :title "Note title",
;; :links
;; [{:id 1,
;; :entitydb/id 1,
;; :entitydb/type :link,
;; :url "http://keechma.com",
;; :user
;; {:id 1,
;; :username "Retro",
;; :entitydb/id 1,
;; :entitydb/type :user}}],
;; :entitydb/id 1,
;; :entitydb/type :note}
Recur-on query
recur-on is used for recursively fetching all the related/nested data (as long as nested data is properly structured).
It is unboundend by default, but can be limited in case of circular relationships.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def recursive-schema
{:folder {:entitydb/id :name
:entitydb/relations {:folders {:entitydb.relation/path [:folders :edges :* :node]
:entitydb.relation/type :folder}
:files {:entitydb.relation/path [:files :edges :* :node]
:entitydb.relation/type :file}}}
(def recursive-data
{:name "Root"
:files {:edges [{:node {:name "File Root: 1"}}]}
:folders {:edges [{:node {:name "1"
:files {:edges [{:node {:name "File 1: 1"}}]}}}
{:node {:name "2"
:folders {:edges [{:node {:name "2 / 1"}}
{:node {:name "2 / 2"
:folders {:edges [{:node {:name "2 / 2 / 1"}}
{:node {:name "2 / 2 / 2"}}]}}}]}}}]}})
(def db (edb/insert-schema {} recursive-schema))
(def db-1 (edb/insert-entity db :folder recursive-data)
(def query [:files (q/recur-on :folders)])
(edb/get-entity db-1 :folder "Root" query)]
;; {:name "Root"
;; :files {:edges
;; [{:node
;; {:name "File Root: 1"
;; :entitydb/id "File Root: 1"
;; :entitydb/type :file}}]}
;; :folders {:edges
;; [{:node
;; {:name "1"
;; :files {:edges
;; [{:node
;; {:name "File 1: 1"
;; :entitydb/id "File 1: 1"
;; :entitydb/type :file}}]}
;; :entitydb/id "1"
;; :entitydb/type :folder}}
;; {:node
;; {:name "2"
;; :folders {:edges
;; [{:node
;; {:name "2 / 1" :entitydb/id "2 / 1" :entitydb/type :folder}}
;; {:node
;; {:name "2 / 2"
;; :folders {:edges
;; [{:node
;; {:name "2 / 2 / 1"
;; :entitydb/id "2 / 2 / 1"
;; :entitydb/type :folder}}
;; {:node
;; {:name "2 / 2 / 2"
;; :entitydb/id "2 / 2 / 2"
;; :entitydb/type :folder}}]}
;; :entitydb/id "2 / 2"
;; :entitydb/type :folder}}]}
;; :entitydb/id "2"
;; :entitydb/type :folder}}]}
;; :entitydb/id "Root"
;; :entitydb/type :folder}
Switch query
switch is used to perform different query based on a given relation entity type, ie in a scenario where
heterogeneous collection needs to be traversed and based on the type of the item in question different subqueries are
required.
Important thing to notice is that, apart from other query-selectors,
switch doesn't move the cursor in graph traversal, rather it points to the current node.
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
(def switch-schema
{:image {:entitydb/id :src
:entitydb/relations {:comments {:entitydb.relation/path [:comments :*]
:entitydb.relation/type :comment}}}
:post {:entitydb/relations {:author :user}}})
(def db (edb/insert-schema {} switch-schema))
(def db-1 (-> db
(edb/insert-entity :user {:id 1
:name "Retro"})
(edb/insert-entities :comment [{:id 1
:body "Comment 1"}
{:id 2
:body "Comment 2"}
{:id 3
:body "Comment 3"}])
(edb/insert-collection :media :media/favorites [{:id 1
:title "Post 1"
:author {:id 1}
:entitydb/type :post}
{:id 2
:title "Post 2"
:author {:id 1}
:entitydb/type :post}
{:src "some-source"
:title "Image 1"
:comments [{:id 1} {:id 3}]
:entitydb/type :image}])))
(edb/get-collection with-data :media/favorites [(q/switch {:post [(q/include :author)]
:image [(q/include :comments)]})])
;; [{:id 1,
;; :title "Post 1",
;; :author {:id 1, :name "Retro", :entitydb/id 1, :entitydb/type :user},
;; :entitydb/type :post,
;; :entitydb/id 1}
;; {:id 2,
;; :title "Post 2",
;; :author {:id 1, :name "Retro", :entitydb/id 1, :entitydb/type :user},
;; :entitydb/type :post,
;; :entitydb/id 2}
;; {:src "some-source",
;; :title "Image 1",
;; :comments
;; [{:id 1, :body "Comment 1", :entitydb/id 1, :entitydb/type :comment}
;; {:id 3,
;; :body "Comment 3",
;; :entitydb/id 3,
;; :entitydb/type :comment}],
;; :entitydb/type :image,
;; :entitydb/id "some-source"}]
Reverse-include query
Includes all entities of a given type that point to the current entity. Based on previous example:
(ns myapp.example
(:require [keechma.entitydb.core :as edb]
[keechma.entitydb.query :as q]))
...
(edb/get-entity with-data :user 1 [(q/reverse-include :post)])
;; {:id 1,
;; :name "Retro",
;; :entitydb/id 1,
;; :entitydb/type :user,
;; :entitydb.relations/reverse
;; {:post
;; {:author
;; {1
;; {:id 1,
;; :title "Post 1",
;; :author {:type :user, :id 1},
;; :entitydb/type :post,
;; :entitydb/id 1},
;; 2
;; {:id 2,
;; :title "Post 2",
;; :author {:type :user, :id 1},
;; :entitydb/type :post,
;; :entitydb/id 2}}}}}
License
Copyright © 2020 Mihael Konjevic, Tibor Kranjcec
Distributed under the MIT License.
Can you improve this documentation? These fine people already did:
Mihael Konjević, Tibor Kranjcec & Mihael KonjevicEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close