@appneurox/connector-service
v0.1.0
Published
Connector Service: NestJS module that runs as its own microservice or inside a modular monolith.
Readme
@appneurox/connector-service
Connector Service as one NestJS module. The same code runs in two ways:
| Mode | How | Routes |
| --- | --- | --- |
| Microservice | node dist/standalone.js, deployed at https://connector-service.appneurox.com | /v1/module, /v1/execute |
| Inside a brand API | servicePackage() mounted by a modular monolith | /connector-service/v1/module, /connector-service/v1/execute |
// Brand API (modular monolith)
import { bootstrapMonolith } from '@appneurox/service-composition';
import { servicePackage } from '@appneurox/connector-service';
await bootstrapMonolith({ services: [servicePackage()] });// Another module in the same process can inject the application directly
import { ConnectorServiceApplication } from '@appneurox/connector-service';servicePackage(options) passes options (extra providers, imports, controllers) to
ConnectorServiceModule.register(), which is how a brand configures this service without forking it.
The host owns HTTP, authentication, tenant context, validation, errors, logging and shutdown
through @appneurox/service-runtime. Importing this package opens no listener.
Status: boilerplate. GET /v1/module works; authorized POST /v1/execute returns
501 NOT_IMPLEMENTED until the business code is written in src/.
Client: @appneurox/connector-service-sdk.
