Operations
This section covers what happens after you ship: how to deploy Nexus to production, how to observe a running system, and how to tune performance when defaults are not enough.
What's in this section
Four pages cover the operational surface of a Nexus application:
- Deployment — OPcache, health checks, graceful shutdown, reverse proxy configuration, process supervision, and resource limits. Also links to platform-specific drill-ins for Docker, systemd, and Kubernetes.
- Observability — PSR-3 logging, per-request MDC context, access logging, async log sinks, and PSR-14 event dispatch for integration with OpenTelemetry and custom metrics tools.
- Performance tuning — Framework pre-binding, OPcache and JIT configuration, Swoole server settings, and Linux TCP kernel parameters. Includes measured benchmark data.
Prerequisites
The operations section assumes you have a running Nexus HTTP application. If you have not yet built one, start with Getting started and the HTTP overview.
For worker pool deployments (multi-core scaling), the Scaling section covers worker pool architecture before you apply the deployment and observability patterns here.
See also
- Scaling overview — worker pool architecture and thread-safe deployment
- HTTP servers — Swoole worker mode vs thread mode tradeoffs
- nexus-logger package — actor-backed async logger