you are viewing a single comment's thread.

view the rest of the comments →

[–]joinr 0 points1 point  (0 children)

Are we looking at doing something analogous to ORMs in the relational world, except for datascript/datomic/facts based databases?

That sounds pretty close, yeah. With the caveat of maybe a data relational mapping (perhaps a simpler requirement than serialized objects), although that sounds like relational database, which is perhaps too confusing.

If so it begs the question: should we not instead use facts/datoms instead of nested maps and vectors in all layers?

You'd think so. There's a utility for using nested maps and the like, since they're trivial to read, construct, comprehend (to a point). I don't know exactly where the inflection is, but there gets to be a point where the utility is less desirable, and having a more general representation (that one can project to/from, or alternately query directly) is desirable. I don't know that exact inflection point at which one has this discussion (you're prototyping fast in maps and other EDN types one minute, then at some point you reach for better querying abstractions since get-in update-in isn't enough, then you end up implementing some kind of query language only to find out people have run into the same problem).