📄️ 1. Logging
It may becomes hard to debug applications running in a distributed manner. Make shure you use alot of debugging!
📄️ 2. EventEmitters
EventEmitters implent the default Observer (or publish and subscribe) Pattern. Checkout wikipedia for a short overview of the pattern.
📄️ 3. Observables
Observables implent the default Observer Pattern. Checkout wikipedia for a short overview of the pattern.
📄️ 4. Create a Dispatcher
To implement the functionalities of NoPE, NoPE creates so called runtime environments. Inside of such a environment the system uses a so-called 'NoPE dispatcher' as a central element.
📄️ 5. Connectivity Manager
The NoPE-Dispatchers uses one ConnectivityManager. The manager observes the connection and remotely connected dispatchers (via their ConnectivityManager).
📄️ 6. Event-Distributor
The NoPE-Dispatcher uses one eventDistributor. The EventDistributor essentially represents a PubSubSystem. It distributes events over the network (or internally). The eventDistributor is essentially a PubSubSystem and can be used to listen for specific events.
📄️ 7. Data-Distributor
The DataDistributor essentially represents a DataPubSubSystem. It distributes data over the NoPE network (or internally). Data is manipulated via JSON pointers (these are structured like MQTT topics; see above). In order to inform systems about changes, subscribers can be informed about changes like in MQTT. The wildcards of MQTT can be used to get the relevant information. I.e.:
📄️ 8. RPC-Manager
The RPC-Manager is used to establish a request-response pattern in NoPE.
📄️ 9.Instance-Manager
The instance Manager manages the instances in NoPE.