Re:ArangoDB: Multi-model highly available NoSQL database
by zbentley on Wednesday January 16, 2019 @08:55PM
(#18927640)
That's because connections (sessions, really, but in practice most things map those 1:1) are the primitives on which Postgres and most other RDBMSes divide their units of transactional consistency--one of their key guarantees. Connections are expensive to create and maintain largely (but not entirely) because of those properties.
[ Parent
| on HN ]
Re:ArangoDB: Multi-model highly available NoSQL database
by thdxr on Friday January 18, 2019 @08:51AM
(#18939255)
This isn't a required design to achieve transactional consistency. See for example how this would be done in Erlang - single connection dispatching to isolated Erlang processes.
Fundamentally just needs isolation to be done at a different layer.