lambdaroyal.memory.abstraction.hierarchie
totally renewed hierarchie builder
totally renewed hierarchie builder
lambdaroyal.memory.abstraction.search
- >>
- >>>
- abstract-search
- break-condition-state
- by-ric
- check-break-condition-reached
- combined-search
- combined-search'
- combined-search''
- concat-aggregator
- filter-all
- filter-index
- filter-key
- filter-xs
- gen-sorted-set
- hierarchie
- hierarchie-backtracking
- hierarchie-backtracking-int
- hierarchie-ext
- inc-and-check-break-condition-reached
- is-stop-feeding-aggregator
- proj
- ric
- set-aggregator
- sorted-set-aggregator
lambdaroyal.memory.core
No vars found in this namespace.
lambdaroyal.memory.core.tx
- *alter-context*
- *gtid*
- alter-document
- applicable-indexes
- applicable-indexes'
- coll-count
- coll-empty?
- Constraint
- constraint-appl-domain
- contains-key?
- create-attribute-index
- create-constraint-exception
- create-no-applicable-index-exception
- create-referenced-integrity-constraint
- create-referrer-integrity-constraint
- create-tx
- create-unique-key
- create-unique-key-constraint
- create-unique-stop-key
- debug
- decorate-coll-with-gtid
- decorate-with-gtid
- delete
- find-first
- get-gtid
- gtid
- gtid-dosync
- Index
- insert
- process-constraints
- select
- select-first
- select-from-coll
- tree
- tree-referencees
- user-scope-key
- user-scope-tuple
lambdaroyal.memory.eviction.core
an eviction channel listenes for successful database inserts/updates and deletes and performs some kind of I/O to them. For instance a concrete implementation could write all successful changes to the in-memory database to a external database to create a persistent version that can be imported during application ramp-up. Eviction channels can be configured to follow certain timing constraints like immediate post transaction eviction or cron like eviction, that is forwarding all the changes every x seconds. Invariants are: (1) Eviction is asynchronous to to the actual transaction, (2) Eviction might fail but to not cause the transaction to fail.
an eviction channel listenes for successful database inserts/updates and deletes and performs some kind of I/O to them. For instance a concrete implementation could write all successful changes to the in-memory database to a external database to create a persistent version that can be imported during application ramp-up. Eviction channels can be configured to follow certain timing constraints like immediate post transaction eviction or cron like eviction, that is forwarding all the changes every x seconds. Invariants are: (1) Eviction is asynchronous to to the actual transaction, (2) Eviction might fail but to not cause the transaction to fail.
lambdaroyal.memory.eviction.couchdb
An Eviction Channel that uses a Couch DB server to load persistent data and to backup all transaction to. The couch db server is supposed to run on http://localhost:5984 or as per JVM System Parameter -Dcouchdb.url or individually configured per eviction channel instance
An Eviction Channel that uses a Couch DB server to load persistent data and to backup all transaction to. The couch db server is supposed to run on http://localhost:5984 or as per JVM System Parameter -Dcouchdb.url or individually configured per eviction channel instance
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close