App 2. Room for the whole stack.

Budget the API and its worker together

App 2 is a useful comparison point for an API with an export worker and a compact database. Give each process a budget and test requests while an export and a release overlap. Keep queue age as visible as HTTP latency.

When to choose a different shape

A noisy worker and a waiting database do not necessarily need the same upgrade. Add memory for observed pressure, reduce unnecessary concurrency, or separate a component when independent operations matter.

Understand the option you are changing

CPU, memory, working storage, monthly transfer and IP choices solve different constraints. Backups are a separately priced option; extra disk alone is not independent recovery. Compare all recurring options before increasing the budget.

Check the next release as well as today’s traffic

Record artifact, schema changes, worker behavior and temporary space. Use the relevant operating guide to choose a measurable next step.

When this profile makes sense

A useful planning baseline for a small SaaS stack. Size your database and workers separately before choosing.

Use a representative workload to validate memory peaks, disk needs, and CPU demand. No benchmark, traffic capacity, or guaranteed application performance is claimed.

What you manage

Choose the Linux image, install and update your application, and keep your own access, monitoring and recovery process. Actual supplier images and availability still need confirmation.