Skip to content

Connector Overview

Connectors are microservices designed to translate events from the NSPS into format-specific requests compatible with external network systems. Each external system requires its own connector.

Role and Key Responsibilities

The NSPS connector handles data exchange between NSPS and external systems. Its primary functions include:

  • Receiving Events: Acts as the entry point for all incoming NSPS events.
  • Data Transformation: Converts event data from NSPS into the format required by the target external system.
  • Authentication: Validates the Bearer token on incoming NSPS requests and handles outgoing authentication to the external system (e.g., token, OAuth).
  • Error Handling and Status Reporting: Manages errors that occur during event processing or interaction with the external system, and reports status back to NSPS.
  • Logging of Interactions: Records all interactions with the external system for auditing, monitoring, and debugging.

The "One Connector – One External System" Principle

A fundamental design principle for NSPS connectors is the one-to-one relationship between a connector and an external system. This means that each external system requires its own dedicated connector. This approach ensures:

  • Specialization: The connector can be precisely tailored to the unique requirements and API of a specific external system.
  • Isolation: Problems or changes in one integration do not affect others.
  • Maintainability: The connector's codebase is smaller and easier to understand, test, and update.