4 ms·
How does this compare to a traditional ORM? I looked through the slides and the paper and this seems to largely provide the same kind of functionality as a regu
by pkage 3y ago
How does this compare to a traditional ORM? I looked through the slides and the paper and this seems to largely provide the same kind of functionality as a regular ORM but with the caveat that you can only do key/value transactions.
- vmfunction 3y agoThink of it like the localStore in Deno. I guess at this point all the lang are going to jump on the band wagon. Why not, all lang should have native KV store. However if we are to jump on in JDK world, persistence is not hard. Java have supurb db like H2 with full postgres compliance, that can be embedded in memory.
- indigo945 3y ago> However if we are to jump on in JDK world, persistence is not hard. Java have supurb db like H2 with full postgres compliance, that can be embedded in memory. H2 is a cute database, but it doesn't even come close to having "full postgres compliance". Besides, it solves a completely different problem from Permazen or JPA - it's a storage engine, not a storage abstraction layer.
- mike_hearn 3y agoTransactions apply across full object graphs. The fact that it uses a KV store under the hood is exposed to you, but it doesn't impose limits. For example if you read an object, read some fields, follow a reference to another object, loop over a list you find there, then make some changes and commit, the underlying transaction will only apply if those operations are conflict free.