How openbackhaul/networkdatalakeproxy works
NetworkDataLakeProxy is a server-side interface that exposes filtered MWDI data and related network-model operations. Its principal workflow accepts an inventory request, resolves the configured MWDI forwarding target, forwards the request, and returns the result; the service also applies ControlConstruct request throttling and schema filtering. The tree documents physical and logical inventory, plus profile, transport, operation, and Elasticsearch interfaces. Some connections are based on import references in the SOURCE INDEX; unsampled implementation details are not assumed.
Main entry points: ElasticsearchClientService.js Elasticsearch service · IndividualServicesService.js Inventory orchestration · RestClient.js REST client · IndividualServices.js Inventory API
Components 23
Inventory workflow
- Inventory API
server/controllers/IndividualServices.js - Inventory orchestration
server/service/IndividualServicesService.js - MWDI request handler
server/service/individualServices/RequestHandler.js - REST client
server/service/individualServices/RestClient.js
Network interfaces
- Profile and service APIs
server/controllers/BasicServices.js - Profile services
server/service/IntegerProfileService.js - Operation APIs
server/controllers/OperationClient.js - Operation services
server/service/OperationClientService.js - HTTP APIs
server/controllers/HttpClient.js - HTTP services
server/service/HttpClientService.js - TCP APIs
server/controllers/TcpClient.js - TCP services
server/service/TcpClientService.js - Elasticsearch API
server/controllers/ElasticsearchClient.js - Elasticsearch service
server/service/ElasticsearchClientService.js
Model and forwarding
- Control Construct utilities
server/service/individualServices/ControlConstructUtil.js - Release handover
server/service/individualServices/BequeathHandler.js - Forwarding automation
server/service/individualServices/PrepareForwardingAutomation.js - Elasticsearch preparation
server/service/individualServices/ElasticsearchPreparation.js
Runtime support
- Configuration store
- Logging
server/service/LoggingService.js
Other components
- Higher-layer consumer
- MWDI
- Elasticsearch
Connections 22
- Higher-layer consumer → Inventory API: requests inventory
README.md - Inventory API → Inventory orchestration: dispatches
server/controllers/IndividualServices.js - Inventory orchestration → MWDI request handler: delegates
server/service/IndividualServicesService.js - MWDI request handler → Control Construct utilities: resolves target
server/service/individualServices/RequestHandler.js - MWDI request handler → REST client: forwards request
server/service/individualServices/RequestHandler.js - REST client → MWDI: sends HTTP
server/service/individualServices/RestClient.js - Inventory API → Inventory orchestration: returns result
server/controllers/IndividualServices.js - Profile and service APIs → Profile services: calls
server/controllers/BasicServices.js - Operation APIs → Operation services: calls
server/controllers/OperationClient.js - HTTP APIs → HTTP services: calls
server/controllers/HttpClient.js - TCP APIs → TCP services: calls
server/controllers/TcpClient.js - Elasticsearch API → Elasticsearch service: calls
server/controllers/ElasticsearchClient.js - Elasticsearch service → Configuration store: reads and writes
server/service/ElasticsearchClientService.js - Elasticsearch service → Elasticsearch: manages client
server/service/ElasticsearchClientService.js - Elasticsearch service → Elasticsearch preparation: prepares index
server/service/ElasticsearchClientService.js - Release handover → Control Construct utilities: queries model
server/service/individualServices/BequeathHandler.js - Release handover → REST client: notifies services
server/service/individualServices/BequeathHandler.js - HTTP services → Forwarding automation: uses automation
server/service/HttpClientService.js - Operation services → Forwarding automation: uses automation
server/service/OperationClientService.js - TCP services → Forwarding automation: uses automation
server/service/TcpClientService.js - Inventory orchestration → Logging: logs
server/service/IndividualServicesService.js - REST client → Logging: logs
server/service/individualServices/RestClient.js