This is an example article describing the platform design. Resource figures will be added only after the actual deployment is measured.
Do the expensive work before publishing
Markdown parsing, frontend compilation, image preparation, and voice generation happen on the main server. None of those jobs need to run each time a reader opens a page.
Serve completed files
The public container runs a Go process that serves HTML, styles, scripts, images, and available article audio. The existing Caddy edge handles public HTTPS.
Measure the real deployment
Idle memory is only one part of the picture. Measure the container and the whole host while pages, images, and recordings are being requested together.