Index
Client workProductionClient engagement — anonymized
Trading Company Site & Operations Backend
Public site and supporting operations backend for a trading company: catalog-style product presentation, structured content management, and a PostgreSQL backend with a dedicated automated backup container.
- Year
- 2025 — ongoing
- Role
- Build, deployment & infrastructure
- Disciplines
- engineering · automation
- Stack
- React · Node.js · PostgreSQL · Docker · Automated backups
01Context
A trading company needed more than a brochure: product presentation that stays current, and a small set of internal workflows that had outgrown shared documents.
02What was built
- //Public site with structured, editable product and company content
- //Operations backend for the internal workflows that replaced shared documents
- //PostgreSQL datastore with a dedicated backup container running scheduled dumps
- //Frontend and backend split into separate containers behind one proxy
03Engineering decisions
Content is stored as structured data rather than blobs of HTML, so the public site renders from a schema — not from whatever a rich-text editor produced.
Backups run in their own container on their own schedule. Backing up to the same box as the database is treated as the minimum, not the strategy.
04Status
In production. Company identity withheld by agreement.