3D-PRMS
One sentence on what 3D-PRMS does and who relies on it. Replace in content/projects/3d-prms.mdx.
- role
- Lead architect
- period
- 2024–2025
- throughput
- TBD
- uptime
- TBD
- stack
- Go, NestJS, Docker, Proxmox
- repos
- 3d-prms-scaffold
Context
What existed before, and why it had to change.
Constraints
Budget, team size, compliance, latency, hardware — whatever actually shaped the design.
Architecture
The services, how they talk, where they run. A diagram or a short config excerpt is worth more than adjectives.
Decisions and trade-offs
Two or three decisions you would defend in a design review, including what you gave up.
Outcome
Measured results only. If a number isn't measured, leave it out.