/ doc / toc / ARCCore / Enum / ARNodeType / ArmDB

ArmDB

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

__TOCDet/Assembly = ARCCore
__TOCDet/Description = A node with a 'client -Subscription-' towards -CoreDB- to a (usually) subset of the entire database (acting as a cache and filtering mechanism), or with a 'client -Subscription-' towards -CoreDB- to the whole database (acting as a cache mechanism only)0x000D0x000A0x000D0x000Aand which stores data as either:0x000D0x000A0x000D0x000A1) -PropertyStreamLine-s (enabling it to servere ordinary continous -Subscription- requests) or0x000D0x000A2) -IP- (typical -PRich-) (enabling it to answer -AdHocQuery-) (the last one is not implemented as of May 2020), 0x000D0x000ANote that since the data storage mechanism in -StreamProcessor- works just as well inside a -Client- node as inside an -ArmDB- node, in many scenarios the -Client- can just subscribe directly to -CoreDB-. In a high-load scenario however it might be useful having a single -ArmDB- node serving several -Client- nodes in order to relieve som load in -CoreDB-.
__TOCDet/DocFragType = EnumMember
__TOCDet/LongDescription = The node will either be based on only -StandardAgoRapideCode- (be -ARADB- configured correspondingly)or also contain end-application specific code (being based on -ARADB-.0x000D0x000A0x000D0x000ANote that in principle this node could also cache incoming data to -CoreDB-. This could be useful in high-load scenarios where -Client- wants to just 'send-and-forget' data. But since the data storage mechanism in -StreamProcessor- works just as well inside a -Client- ndoe as inside an -ArmDB- node, there would usually be nothing in the way of -Client- caching itself, without any need for -ArmDB-.
__TOCDet/Name = ArmDB
__TOCDet/Namespace = ARCCore
__TOCDet/Type = ARNodeType
__TOCDet/Attribute/Description = A node with a 'client -Subscription-' towards -CoreDB- to a (usually) subset of the entire database (acting as a cache and filtering mechanism), or with a 'client -Subscription-' towards -CoreDB- to the whole database (acting as a cache mechanism only)0x000D0x000A0x000D0x000Aand which stores data as either:0x000D0x000A0x000D0x000A1) -PropertyStreamLine-s (enabling it to servere ordinary continous -Subscription- requests) or0x000D0x000A2) -IP- (typical -PRich-) (enabling it to answer -AdHocQuery-) (the last one is not implemented as of May 2020), 0x000D0x000ANote that since the data storage mechanism in -StreamProcessor- works just as well inside a -Client- node as inside an -ArmDB- node, in many scenarios the -Client- can just subscribe directly to -CoreDB-. In a high-load scenario however it might be useful having a single -ArmDB- node serving several -Client- nodes in order to relieve som load in -CoreDB-.
__TOCDet/Attribute/EnumMember = ArmDB
__TOCDet/Attribute/EnumType = ARNodeType
__TOCDet/Attribute/LongDescription = The node will either be based on only -StandardAgoRapideCode- (be -ARADB- configured correspondingly)or also contain end-application specific code (being based on -ARADB-.0x000D0x000A0x000D0x000ANote that in principle this node could also cache incoming data to -CoreDB-. This could be useful in high-load scenarios where -Client- wants to just 'send-and-forget' data. But since the data storage mechanism in -StreamProcessor- works just as well inside a -Client- ndoe as inside an -ArmDB- node, there would usually be nothing in the way of -Client- caching itself, without any need for -ArmDB-.

Edit single sub keys only: __TOCDet

Generated 2024-06-01 19:10:20.945 UTC