Node.js · Containers · AWS target

Legacy Application Modernization

A constrained order service modernized without losing its HTTP contract. The implementation adds secure container behavior, PostgreSQL integration, recovery evidence, and an explicit AWS target architecture.

Scope: Modernization waves 0–3
Evidence: Local lifecycle and hosted CI verified
Boundary: AWS Terraform target remains unapplied

The modernization path

The original API contract remains stable while validation, idempotency, ownership, state transitions, and safe error envelopes become explicit. A non-root, read-only container packages the application with health and readiness boundaries.

Operational seams cover PostgreSQL, JWT identity, queues, object storage, telemetry, graceful shutdown, backup, restore, and recovery. Each claim is tied to repeatable evidence rather than the presence of a diagram alone.

Architecture

Preserve behavior, improve the operating model

Open full-size SVG →

Application behavior, PostgreSQL integration, container acceptance, security scanning, and recovery drills are verified. The depicted AWS services remain a reviewable target.

Engineering decisions

Contract continuity: modernization does not silently change consumer behavior.
Runtime hardening: the image runs without root privileges and with a read-only filesystem.
Recovery evidence: backup and restore are exercised alongside the normal path.
Truthful architecture: planned AWS resources remain clearly distinct from verified runtime behavior.

Review the modernization evidence.

GitHub repository →
Architecture documentation →