Root / Assembly / ARCCore / AREnumType / DocumentationOnlyEnum / ARNodeType / _Member / ArmDB
|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)|
and which stores data as either:
1) PropertyStreamLines (enabling it to servere ordinary continous Subscription requests) or
2) IP (typical PRich) (enabling it to answer AdHocQuery) (the last one is not implemented as of May 2020),
Note 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.
|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.|
Note 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.
Generated 2020-10-13 11:11:01.276 UTC