@openapi-typescript-infra/service
v5.5.1
Published
An opinionated framework for building configuration driven services - web, api, or ob. Uses OpenAPI, pino logging, express, confit, Typescript and vitest.
Downloads
1,901
Maintainers
Readme
@openapi-typescript-infra/service
An opinionated framework for building high scale services - web, api, or job. Uses OpenAPI, pino, express, confit, Typescript and vitest.
This module creates an environment that makes it simpler to host a REST service (less repetition, more enterprise grade features). Wherever possible, we use off the shelf infrastructure (OpenAPI, Express@5, Terminus are examples). The goal is to allow you to enjoy a high level of type safety with a low tax in type construction in a microservice environment.
The module takes care of configuration-driven:
- body logging
- json parsing
- error handling
- hosted OpenAPI documents/handlers
- traditional routing
- graceful shutdown
- health checks
- Telemetry and instrumentation
services built with this module use Typescript with Node 18, which involves transpilation. This module takes that into account across the development and production experience. It does not currently use ESM for the most part, because between OpenTelemetry, eslint and the package ecosystem, that is currently a pipe dream, or at least something that requires incredibly precise configuration, which is not the intent.
This module has the following core functionality:
- Loads multilevel environment aware configuration, merging configuration information as appropriate to yield a single hierarchical configuration store. We use a modern port of confit.
- Engage OpenTelemetry for tracing and metrics monitoring (via Prometheus-format metrics) and wire this into JSON-based pino logging.
- Setup an Express@5 application with common service hosting options such as body parsing, error handling and graceful shutdown.
- Find and load route handlers and static content serving, if desired.
- Validate and load OpenAPI 3 specifications and wire up methods to path-based route handlers including support for authentication.
- Launch a second express app to serve health checks and metrics
- Setup infrastructure for interservice calls with tracing.
- Provide a central service runner that handles loading your service and getting to a running state in both development and production environments.
Please see the plop-based project builder for an easy way to build an example project.