OptionalfrontsOptionalowntrue: front k listens on the port of its options + k, as where there is no SO_REUSEPORT, so that a client chooses its front
the module a front imports to configure its OPCUAServer: its default export, called with
serverModuleData and { front }, returns the OPCUAServerOptions of that front. Each session
worker calls it too, with { front: -1, sessionWorker }, for the onCreateMonitoredItem and
onDeleteMonitoredItem hooks, which run where the monitored items are; it uses nothing else.
Optionalserverpassed to the default export of serverModule; structured-cloned to each front
Optionalsessionhow many session worker threads host the subscriptions of the sessions; 1 by default
Optionalsessionthe session worker script, for a bundled deployment; this package's by default
Optionalworkerthe front worker script, for a bundled deployment; this package's by default
how many front threads; 1 by default. A machine given to this server alone may take
os.availableParallelism() - 1: one core is left to the engine, which applies every write and pushes every change. A read-mostly server gains up to one front per core. Each front needs a few client connections of its own (Linux spreads connections over the fronts by hash).